Ensuring a Flow Step runs only after the previous has finished

I have a flow with multiple steps, but I would need some of the steps to only be run after the previous step has completed fully.

As an example, I'm adding some master data from Business Central into Plytix (a PIM platform), and Plytix returns the id for the newly created record. Because there's some Parent/Child relationship between some Business Central records, I need to make sure all Plytix IDs have been fed back into BC, before running my next step to fetch the children records with their respective Parent Id.

My flow is currently failing because Celigo is running steps at the same time, and by the time I'm fetching the Parent IDs on the children, the Parent IDs are still not there.

I read something about creating multiple flows for this, but I have a few filters I need to run in the beginning of the process to identify which records are eligible to be updated in this flow, and if I need to run a separate flow, those filters will no longer be valid (I basically filter where Plytix Id is blank -- at the end of the first flow, Plytix Ids will no longer be blank).

How can I accomplish this without having to create multiple flows?

0

Comments

4 comments
Date Votes
  • Marcelo Borges the are only a few ways to do this.

    1. If there isn't much data exporting from your source application, then you can set a very large page size so that all records fit within 1 page. Celigo works off of pages of records so by doing this you would accomplish what you want. However, if you have a lot of data from your export, you would end up with multiple pages of data and then this may not solve your use case.
    2. Use multiple flows. To do this, at the very end of your first flow, you would dump the data you want to pass to the next flow into a S3 bucket, ftp file, google drive file, etc.. The second flow would pick that file up and continue processing.
    3. Create a myapi that is called from the flow itself where the myapi can handle multiple requests in a row for the same records before moving to the next set.
    1
  • Thank you for the prompt ideas, Tyler. I'll look into the myApi option to see what I can get out of that. 

    Has this type of request been made as a possible improvement on the platform? It would be great if some flow steps had a flag determining they cannot be run until all previous steps have been processed.

    TY

    0
  • Tyler Lamparter, using the Page attribute actually helped a lot here. Thanks for that tip!

    0
  • Marcelo Borges good to hear

    0

Please sign in to leave a comment.

 

Didn't find what you were looking for?

New post