so far i'm using javascript flow to refresh all aggregate simultaneously.
but it's not efficient because if there's a lot of aggregate you need more to create a client action.
maybe like this
Sorry but I could not understand cleary the scope of your idea! Can you detail it?
Regards
I don't understand your idea.
You can add as many refresh aggregates in ONE client action. No need to create one per aggregate.
I think in case if you are using Fetch data from Other Sources Action in Data Action Events On After Fetch action can be refresh All Aggregates.
yes we can add as many refresh aggregates in ONE client action. and outsystems run from flow start down to flow end, and it takes turns. but when in an aggregate with a lot of data then outsystems will wait for the flow to finish refreshing the data after that it continues the flow below it. not refresh all aggregate simultaneously. sorry my english is bad.
so I mean, I want to refresh the data at the same time without waiting for the flow refresh aggregate to be refreshed because the data in the entity is too much, it feels when I'm developing a lot of charts.
Aggregates refresh are executed asynchronize
@Daniël Kuhlmann ,
i had noticed a while ago that this doesn't seem to be the case, they seemed to only get executed simultanously at start, not when refreshed within the flow of an action.
So, I decided to do a test, these are the results :
I record the timestamp the event happens that triggers the fetches, the start timestamp on server side, and the timestamp the onafterfetch starts.
You can see that on test 2, B only starts after A is done, on test 3 A only starts when B is done. At Start and with a hack as suggested by Extenv, they start simultanously.
Dorine
Thanks @Dorine Boudry you are right
@Dorine Boudry thanks for the clear explanation.
Best Regards
@Dorine Boudry Thanks for helping explain.
your is the only good trick to do it
