-
Well - if you can narrow down the submit commands that are causing the issue, that may give some clues for tracking it down.
-
There goes that idea - your schema is too large for me to just scan it and see if something is missing, especially since I have no idea what mappings out of all of them are the new mappings, or what are the newly added fields.
-
Form Options > Versioning
-
I wonder - is your form set to update existing XML under Versioning? It could be that the old XML are missing some of the newly added nodes.
-
Did you add any new mappings when you modified the template? Change the main data source at all?
-
If you use now() in a formula to create the form name, yes, that will happen. I usually add a field to the form for the form name, and add a form load rule to set it with the condition that the field is currently blank. Then now() will be when the form is first created, and stays stable.
Edited for clarity: I mean, if you use now() in a ...
-
Save the attached file locally and then right click and select design to open in design mode. From there, you can see the rules I put on current company and preview to check it out.
-
I'll have to see if I can repro this - I'll try to get to it later today / early tomorrow.
-
Care to share your form?
-
Well - if it had code, I'd guess the sandbox worker process had been timing out when publishing to the library....