In front end workflows it isnt a problem because the data definition from the API call is explicitly available to use in expressions.
For backend workflows the api call return objects are not available.
previously I have used a front end workflow to call schedule api workflow on a list. This works if you dont care what order the objects are created in.
In this case I need to sequentially order the objects so I call the backend workflow recursively. I have used the method of sending in a list of parameters for each of the fields on the object and recursively taking the first value and creating a db object for it.
But now Im faced with a nested json structure and it doesnt really work to do that. The nested objects dont need to be numbered/ordered.
Is there a standard way of solving this?
Im considering letting my original API call create the numbering, but that creates a bit a race condition if other people are creating objects at the same time.