You assisted me about 6 months ago in getting an API connection up and using Repeat Function oAuth2 connection - Cornerstone(CSOD).
It is working like a charm. Thank you
I am trying to add multiple path’s, not sure how to go about it.
I tried to add Web Iterate before the Repeat, but that did not work.
I apologize, but based solely on the screenshots you provided, it's still unclear what you are trying to achieve.
In our previous discussion, you were creating a workflow to retrieve a paginated response from the API. Can you provide more information about what you mean when you say "I am trying to add multiple paths" in this context? Are you attempting to send multiple requests to the same API endpoint but with different parameters, such as "GET /api?q=vw_rpt_123" to retrieve all data, followed by "GET /api?q=vw_rpt_998" to retrieve all data from the second response, and then consolidate the rows from both responses into one table?
Up to now, I developed an EasyMorph for each endpoint.
I prefer not to build a separate endpoint for each one.
This is for initial data extraction.
I have about 128 endpoints to read, and extract data.
This is what I want to achieve:
I want to iterate through path vw_rpt_123 and get the results and save the file as dset.
Then I want the Easymorph to go to the next path vw_rpt_998 and retrieve the information and save it to a dset
Placing the EasyMorph file with 1 path on the server worked perfectly.
I will attempt to do all 128 endpoints in one EasyMorph but would like to combine some of the Endpoints to reduce the EasyMorphs I have to build.
Modifying the ‘Repeat’ action so that it could somehow consume multiple paths is tricky, as it would conflict with the logic of the Repeat action itself (in particular, that the output of each iteration is the input of the next iteration).
My advice would be to further encapsulate the above, so that if you had a table that retrieves the data by calling the Repeat action and passing a path and token to it, you will now move that table into a separate module, and call that module from a table containing multiple paths (just like in your screenshot) using the Iterate action in ‘Iterate and append results’ mode.
You can pass the path and token to this module as parameters:
You will also need to create the aforementioned ‘path’ and ‘token’ parameters in this new module, and to pass these parameters as a table to your already existing ‘Repeat’ action, you could use the ‘Parameter table’ action in this new module.