Requesting Admin to move this to the ARS Space.
Just moved this discussion. Thank you
In that case I would probably put the content of the whole Results into one field and run a loop (guide) through the values (cut them out one by one using string operations). In each loop you can do then whatever you need.
btw-what if you map e.g. 20 elements to 20 fields and in the response you get only 10 ? Do you get then an error ? (sorry I didn't test this). if you don't get an error, then you can map the highest number of possible values and if there will be less, then the fields will be just left blank. but this will probably throw error .....
Such approach could also help when amount of responses is greater than amount of available fields but response is still considered valid (e. g. instead of preparing static number of fields for responses, each instance could be recorded separately in another form), though if external service is unable to restructure message, can REST API ignore resultN parts and map results to single field on its own? On the downside, (I'm assuming that) tables and table loop guides would not be applicable, so custom workflow would not only have to split results into constituent parts, it would also have to include handling of special characters and that could be the trickier part to implement correctly.
Thanks for the response!
I was afraid this would be the anwser and I'm probably going to have to work around this, but thanks again anyway.
If 'results' is an array, you can map the output of that to another form, and with that, for each 'record' in the array, it'll create another record from 0 to n records, you can then do whatever you want with those results.