-
So, yeah, your helper field needs to also be in the data connection to the list. You may need to walk through the data connection again and include the version field so you can repurpose it. Then, put the rules to set the CAML data source and execute the CAML submit on the version field. The version field will be inside the same repeating group ...
-
SharePoint server. This link has more info https://support.microsoft.com/en-us/help/896861/you-receive-error-401-1-when-you-browse-a-web-site-that-uses-integrate
-
Is your repeating table bound to the SharePoint List? Or to the main data source?
-
Yeah, the usual approach to this is to disable loopback on the server (which is the unsecure way to do it, but usually when you find the instructions for that, you can find the instructions for the right way!) - but I've not worked with on-prem SHP 2016, so I'm not sure if this is going to be the same there....
-
So - you are able to add code to your form? If so, you could just use code to add the instances of your repeating node that you need, based on the number entered. If not, you could use default data for this - add the max number of rows you'll let the user add to the defaults, then display them based on the entered number. Let me know if ...
-
Perfect, and thanks for posting your solution!
-
Oh interesting. I think I'd use a repeating structure for this, if you weren't already planning on that - under Data in the ribbon, find the default data option and you can insert additional instances of a repeating group so that you can default to having 22 available. I'd probably use a dropdown for the selection of the number, and I ...
-
I see in our DBXL Release Note documentation that this can be caused by .NET 4.5.1 not being installed. Can you verify that version (or later) is installed?
-
You are using your main data source to query for the item you wish to update? The fields on your form are bound to the data fields in your main data source? Feel free to attach your form under the Options tab in a reply if you'd like me to take a look.
-
Is your repeating table bound to your secondary data source? I'm guessing it is... if so, you can repurpose a field you aren't going to need for your CAML mapping, like the version field or something - and put your submit rule on that repeating field. Then for your logic, set the field to something it would never be. In the case of ...