InfoPath Dev

Alright, looks like I was able to get it fixed through trial and error. If anyone else has this issue, try to add a random text field and hide it. It magically fixed my issue and I'm not sure why. Unless anyone has an explanation for this weird behavior, the thread can be closed.

Hilary - I am having the same issue in sending an email from InfoPath 2013 using Office 2016 suite. I've both 64 bit but cannot down with 32 bit version hence client need. During submit an email error pop up the parameter is incorrect. One resoution I got from Microsoft to make email functionality operiotional for InfoPath 2013 and Office ...

Bonjour Dans mon formulaire InfoPath j'ai un tableau extensible rempli via une connexion de données SQL (secondaire) , mais j aimerais y ajouter une contrainte via une variable ( ou autre) en fonction de la valeur d un champs de ce formulaire ! Requete connexion de données secondaire du tableau extensible : (je ne sais pas si c'est ...

Our InfoPath forms are not browser forms.  We view them in Office 10 & Office 13 InfoPath filler.  When we open them on any Win10 machine, the form width becomes very narrow and all of the text is smooshed together. I have changed the scaling settings in Win10 and also tried to turn off DPI scaling ...

I'm working on a fairly complex InfoPath form and ran into an issue this morning after I added a multiple-selection list box and tried to populate it using a filtered data connection. After I added this and published it to a SharePoint site, the form appears to send postbacks over and over until it hits the server limit, no matter how high ...

Oh - so the rule is from a workflow? You may need to walk through the publish wizard and when you reach the promoted properties screen, change the promoted View_Change field to allow it to be edited in library. :)

To troubleshoot, I'd probably put the query fields on the form temporarily, and add a button to execute the query - see what happens?

I'm trying to do something similar, but not sure how this solution applies to my context. I am returning data from an SQL query, and attempting to use a filter to return the data from the SQL query only when one of the columns matches the accountID of a person field @COLUMNA[COLUMNB = AccountID] in my form My problem is in the SQL ...

 Hi Hilary. To be fair this is probably more of a Nintex question now I think about it, but I've attached the form anyway in case you can think of any thing. Thanks again for your help.

Thank you!  Your instructions work, and yes, it is a tough design.  I will do it the cludgey way for now and learn about using another list to create cascading dropdowns with XPath filters for our next iteration.  Thank you so much for your guidance, it has helped tremendously. Cheers!