It looks like you have two DataSource steps, one for each entityId and entityType? This is not necessary. You should have one XML DataSource that can provide both. That might be causing the issue you are seeing.
groovyguy - Your assumption is correct in that the number of records is not always the same.
I do recognize the ability to get a specific number or records from specific nodes using XPath statements, but I was hoping for an easier way. Unfortunately, I do not have much knowledge when it comes to groovy. Thanks for your help though!
jg0888: It's been awhile since I've worked with a Data Sink and a file, so I am not 100% certain, but I believe it appends data to the file instead of overwriting it each time. If that's the case, uou might be able to set up a DataSource and DataSource Loop to achieve the desired results.
With an XML DataSource, you can set up an Xpath statement that'll select the elements required, and using the loop would parse through all of the available objects. This is how I think it could work laid out in test step order:
This may take a little bit of trial and error, but it'll dynamically store the records from the response via the XML Data Source loop. No groovy required at this point.
groovyguy - Thanks for the suggestion. I was able to create a DataSource from the get XML response, and then pull information from there. This proved to be a lot easier than pulling directly from the Soap Request test step.
However, I am seeing that it is skipping every other value although my DataSourceLoop test step iteration is set to only 1. It looks to be every other from what I can tell which is very confusing. Also, it skips depending on which DataSource step is chosen.
Any idea why this would happen? I can add any additional screenshots or information that you might deem helpful from my source. Attached what my SoapUI Pro Test Steps look like.
It looks like you have two DataSource steps, one for each entityId and entityType? This is not necessary. You should have one XML DataSource that can provide both. That might be causing the issue you are seeing.
groovyguy - Thanks!
Also, I was realized looking through a couple other posts in the community, that my issue was DataSource Step and Target Step were the same. After changing this so that my Target step was the step AFTER the DataSource Step, it is working as expected.
Attached final configuration that worked in case anyone else wants to do something similar in the future.
