-
Your rules are on the field you wish to set (this is a common mistake, I used to do this all the time!) and they need to be on the fields that will be changing. That is, rules fire when a field changes, so you don't want them on your target. Instead, put the rules on NRD CPQJ.
-
If you are using a browser other than IE, or typing things up in some other application and pasting in that may cause the issue. If you attach a copy of your form under the Options tab in a reply, I'd be happy to give you a hand.
-
Yes, I understood this - were you able to put the batch node on your form? Is the data populated both in the browser & in preview?
-
So - are you looking to create a calculated column in a SharePoint list that reflects this formula? Or are you working on an InfoPath form and need help with the logic to set the field? If this is in InfoPath, you'd use rules with conditions to accomplish this. If you attach your form under the Options tab in a reply, with some info on what ...
-
If your web service submit is submitting the batch node, you'd expect to see the values there in the list - since your form is succeeding in Filler, you could always verify this in preview.
-
So - how are you submitting to the web service? Usually, I have a secondary XML data connection with a node called "batch" that has the various fields being set for the submit. I'm suggesting you drag that node onto the form so you can see the values - does that make sense?
-
Oh interesting! And the batch node that you are submitting showed the values you expected to be submitted?
-
Let's see. I would try to test just the list submit. I'd add the batch node that you are submitting to the form so you can make sure it is populated, and add a button to just execute the data connection... maybe see if that reveals anything? Anytime I've run into this, loopback check is disabled on the server and I get an error in the ...
-
You'll have to promote the fields you want to see to the library. You can do that when you publish - don't use quick publish, but walk through all the steps and there will be a dialog for selecting the fields you want to promote. MS Flow will work with document libraries, but you may need to type in the library name instead of being able ...
-
I would expect an error if this was a server configuration issue. This isn't Office 365, is it? If not, I'd try again and check the ULS logs on the server....