InfoPath Dev

I have it for my benefit... basically for testing so I can see if everything is moving and changing as it should.  

So - silly question - but why do you have a hidden section with a table? Do you need to be able to see all the data?

Hi all, I'm very new in using InfoPath and has been googling/searching on this forum for my issue. Hopefully someone can help. On my form, I have a very long list for the user to check off for their selection (52 items). My first question is if it's possible to have the multiple-selection list box in multiple columns. I've ...

Right, feasibly you wouldn't have that many. I only ran into it because I was running a query on a secondary datasource (SharePoint list) where I needed to bring all my list fields in (in a section hidden to the user), in order to use the CopyTable qrule for something I needed to perform. I was able to get rid of a couple ...

 Oh wow - I've never seen that before! I guess I've never needed to create a repeating group with that many fields. I'm guessing that is just an arbitrary high end they selected when they designed the product. And even if you add more fields manually to the repeating group, the repeating table will only contain the first 63 if you ...

We found that the form was actually working on one FE Server and not the other.   After much sleuthing, we found that the host file on the FE Server where we would get the timeout error had an incorrect ip address active.  We commented out the ip address and the form works properly on both servers.  Thanks for your help, Hilary!

 You are 100% sure you have the right field names in your CAML? Perhaps try just setting the Title field to start, comment out the other fields, and see what that gets you.

Hi, I have followed all the steps carefully, however the data connection is not submitting data to my SharePoint site, even though no error is shown. CALM is verified, GUID is correct, connection is well set up. Have you come across a case like this? I am using SharePoint 2013 and InfoPath 2013. Regards,

Are you able to set this up in a dev / test environment so you don't have to try to troubleshoot in production? I'd probably start by disabling the workflow entirely, or temporarily removing the update event from it, just to narrow it down...

Hooray! Glad you have it working. :)