-
Are you publishing directly to a form library?
-
I'm super confused, sorry. I thought you said you had injected the form with the Admin option.
You can change the selection of those options in the injector. I just want you to try your form injected as Browser / Sandbox rather than Browser / Admin (which is I thought you were saying you had chosen?)
-
Okay. Generally, I have found adding to be okay in browser forms w/ code or qRules, but removing will cause schema validation errors. Can you put the removed fields back into the data source? You can download one of your existing XML and open in a text editor if you need to see the exact name / location of the removed fields.
-
Did you happen to make any changes to your main schema at the same time as making the change to add qRules? Specifically, did you delete any nodes or move any nodes in the main data source?
-
I wonder if you need to disable loopback check on the new server.
-
Have you been able to use the Lists web service from a browser form in your environment before?
-
Great, thank you. Can you try injecting without using the Admin option (Browser / Sandbox) then add a rule to QdabraRules finishedLoading attribute that when finishedLoading = true, set useWebServices (in the QdabraRules Form group) to true?
Then try again in the browser - this will make the form use web services like it does in preview. You ...
-
Oh, and do make sure to disable your Close the form rule prior to publishing so you can test in the browser and see if there are any errors in the Error node.
-
I think that is because you have @useBrowserApi set to true - I'd expect this error in preview in that case. Can you change that rule to set @useWebServices instead, verify in preview, and if there are no errors, publish to SharePoint?
-
Have you had a chance to try Ernesto's suggestion?