Hi All,
I'm using a data fetch to return the results of various aggregates. Due to the way some of the front end screens are optional, one aggregate will not always run. If this happens if seems as though nothing is returned from the data fetch at all even though some aggregates have run.
Why is this and how do I get around it? Do I need to split out the optional aggregate in to it's own fetch action to prevent this behaviour?
Thanks
for starters, in Reactive, it is not advised to have too much aggregates bundled up like that in a single fetch. What is the reason you are doing this ? So maybe the simple answer is : yes split things up.
But even with all of them in a single data action, what you describe doesn't sound right to me.
Can you share more details, like how exactly it regulates which part of the aggregates are executed ? If you debug, do you see the flow you expect, with the other ones executing ? Do you see data in the output of the data action ?
Dorine
Hi @JayPea,
You can split your Data Action into separate aggregates, and it would be beneficial for you to use aggregate directly rather than putting it into a Data Action unless you need it to be like that.
OutSystems applications are smart enough with Aggregates and will only pull the required data, which might save you some Network bandwidth and improve performance.
Regards,
Prakhar Sharma