In my organisation, we are using Nintex Enterprise. I have been asked to review a form using web request controls.
The problem has been reported that the XPath for value (//ClientNumber) that has been saved to the list, does not match the XPath for display (//FullName) that has been selected in the control. For example in the database we have:
Client number - Full name
12345 - Bill Gates
56789 - Anton Gates
So, when in the control the name Bill Gates is selected, the corresponding client number that gets saved to the list might be 56789. It seems from one item the name has been saved to the list and from the item below/above that, the number has been saved. This has happened very incidentally. I thought of multithreading but it seems too coincidental that when this happens the last name is (partially) the same.
We can't find any fault in the service url or the database (view) itself.
I think the problem might have to do with a JavaScript function that is active on the form and that I have very little experience with. The client-id of the web request control is saved to a JS variable (ClientNumber1). Example of the Javascript:
if(ClientNumber1.indexOf("_hid") > 0){
ClientNumber1= ClientNumber1.substring(0,ClientNumber1.indexOf("_hid"));
}
$('#'+ClientNumber1).combobox();
With this combobox users can search clients on (part) of a name.
It is also worthwhile to mention there are 3 client lookup web request controls on this form.
Could this setup somehow switch out the index or something?
Any ideas would be much appreciated!