Form not updating XML in request
I've noticed some inconsistencies with regards to plugging values in the form in SoapUI and it actually updating the XML underneath. In the screenshot I have attached, you will see that I'm requesting a set of items from the service. There are four "Groups" in this request however, as you can see, it's not returning the set properly. So if I ask for 1 record, starting at the first record, it may work. When I update the form to return 1 record starting at index 2 (3rd item), it's not returning the correct result set. I noticed the reason for this is because the actual XML request being sent was not updated with the parameters I provided in the form. Deleting and re-adding the component in question "fixes" this but invariably, eventually, the form "loses connection" with the XML data.
Is this a bug or is there something we're not getting about updating the XML? What I do is, set the focus in the field, delete the value by selecting it with my mouse and hitting the delete key, then typing in a new value, then I've tried any one of the following to "save" the current state of the form: 1) hit the tab key 2) hit the enter key or 3) click on the validate button. Neither of these three "methods" to get the change to persist seems to work after SoapUI "loses connection" between the form and the XML.
Once SoapUI gets in this state, there doesn't seem to be a way to correct it other than deleting the component from the form, then re-adding. That's acceptable given the small amount of data required in this instance but if there is a node level that has many values in it (in our case, contact data has a couple dozen fields (firstName, middleName, lastName, Address1, etc.), this gets to be a significant inconvenience.
So, what is the correct way to update the form such that the XML actually gets updated prior to sending the request?
Is this a bug or is there something we're not getting about updating the XML? What I do is, set the focus in the field, delete the value by selecting it with my mouse and hitting the delete key, then typing in a new value, then I've tried any one of the following to "save" the current state of the form: 1) hit the tab key 2) hit the enter key or 3) click on the validate button. Neither of these three "methods" to get the change to persist seems to work after SoapUI "loses connection" between the form and the XML.
Once SoapUI gets in this state, there doesn't seem to be a way to correct it other than deleting the component from the form, then re-adding. That's acceptable given the small amount of data required in this instance but if there is a node level that has many values in it (in our case, contact data has a couple dozen fields (firstName, middleName, lastName, Address1, etc.), this gets to be a significant inconvenience.
So, what is the correct way to update the form such that the XML actually gets updated prior to sending the request?
