-
I'd need to see your form to find the issue. You can attach it under a reply on the Options tab.
-
You can find an outline of logic for this here: https://social.msdn.microsoft.com/Forums/en-US/b72c47ad-4f83-49db-8372-3e336c2e1cde/infopath-rule-for-calculating-business-days?forum=sharepointcustomizationlegacy and I am also attaching a sample form with this logic implemented that came from this post: ...
-
We've used receive connections to our SOAP service instead of submit so that we can get back the error info, as well as some other identifier information returned by the form. That may require code, however, depending on your web service, for passing in the form XML as a string, I'm not sure on that.... You could also use validation rules ...
-
Did you try just manually copying the forms into the new library and using the Relink view (may have to switch to classic view to find the Relink view, if your library is in modern). When the XML were created, they get a URL to the form template they are supposed to open with, so my guess is that these XML are still opening with the old form.
-
Thanks, that helped me find the issue. You need to set your daysOfTheWeek data connection to run on load is all. See attached screenshot. Just modify the data connection, click through the wizard and be sure to select the checkbox.
-
I am asking where you found the logic you are using in the current calculation so I can better understand it. I am assuming you did not develop these formulas yourself. What tutorial did you follow, please?
-
I'm sorry - without seeing the form I'm pretty much out of guesses. It sounds like the library is the issue? When you publish to a new library the form works in the browser? If so, you may just want to start using the new library. You can copy all the files over from the old library and relink them in the relink view.
-
Can you direct me to the instructions you followed for the logic currently in the form, so I know what to check it against?
-
Does your form have code in it? Or did you maybe add code accidentally?
-
Again, I wouldn't expect any of these warnings to prevent the form opening the browser. The compatibility is still set to browser enabled? That's also under form options. You may want to make a copy of the form and publish it to a test library, then you can try removing things from the form to narrow the issue down. You could also try ...