in ION, Can you run a dataflow using more than one trigger point ? example two API Trigger points

kamal nasr · 2024-10-28T17:39:09+00:00

There was an error rendering this rich post.

I have a dataflow running on the last day of the month, using an API call with a cron expression.

The cron expression is "0 15 2 L * ? *" for some reason it is impossible to cobine L with any numbers "1,L" and "L,1" will not work.

Is there any simple inteligent way to stop us having to have another inslance of the dataflow runing with a diffrent Cron schedule ?

Kindest regards ad thanks in advance for your answers

Find more posts tagged with

Accepted answers

Brandon Watson

https://community.developer.infor.com/discussion/222/in-ion-can-you-run-a-dataflow-using-more-than-one-trigger-point-example-two-api-trigger-points

No, you cannot do that with Quartz Cron schedule. You would need to have two separate triggers. Unless you could have it run every day, then do a check if it is the first of the month or last of the month, and filter based on that.

All comments

Brandon Watson

https://community.developer.infor.com/discussion/222/in-ion-can-you-run-a-dataflow-using-more-than-one-trigger-point-example-two-api-trigger-points

kamal nasr

Hi Brandon,

Thank a lot for that, this is really helpful, as I am a novice in ION do you have examples on these two solutions ? i am downlading a jason file that contains currency rates

Kind regards.

Brandon Watson

I don't have an example of the second solution but would probably use Python to ensure filtering properly. The first solution is straightforward as you just add another API item in your Connection Point.

rafael_falco

Hi… Have you tried using activities in parallel?

kamal nasr

https://community.developer.infor.com/discussion/comment/320#Comment_320

After adding a new api connection point i get the following error:

The document and scenario combination ‘SyncXERatesSEND’ must be unique.

Brandon Watson

https://community.developer.infor.com/discussion/comment/350#Comment_350

Sorry, I was afraid of that. I had thought it was an old on-prem thing only, but apparently is a Cloud issue too. I created two separate BOD's for my old project.