-
My guess would be something in your rules / defaults is causing a loop that wasn't getting caught in 2013 but is in 2016. Do the fields with default values that are getting updated have rules on them?
-
I'd probably see if one specific query was causing the issue by disabling all rules on the button and re-enabling one at at time. Do you get any additional messages in your logs when the error occurs?
-
I would start by comparing the InfoPath Forms Services settings between the two servers. Any differences?
-
Sorry I'm so slow to reply to this - It sounds like you have a layout or filtering issue. If you are still having trouble, can you attach a copy of your form to a reply under "Options"?
-
Well - I replied THEN thought of this: https://msdn.microsoft.com/en-us/library/office/ee527346.aspx - try checking the IsNew property. :)
-
I'd probably add a field in the main data source to track this - like a status field that defaults to blank, and your C# code can set it to "Not New" or something, then can check for that value prior to running.
-
Wow - I'm at a loss. You've tried this on more than one machine, same results on all? On mine, with my test form, I don't have the issue at all. Attaching a screenshot w/ version numbers just in case it is helpful.
-
Oh, I see - it doesn't matter what the XSN is, you have the same issue. Silly question, what version of InfoPath / Office are you using? I've got 32 bit on my current machine, but my old laptop has 64 bit.... are you using 64?
-
Where is the XSN the XMLs used published to?
-
So - just tried this with a simple form I created (it had one field). I opened the form, filled it out, saved the XML. I ran the script, changing it to the folder I'd saved the XML in - no issue at all. If you just manually open one of the XML in c:\temp\xml, does it open w/out issue?