This content has been marked as final. Show 2 replies
I would like to try out the effect on the size of my current document of an aggregation: The Dashboard I am building is for management - plus one colleague, and only that one colleague needs the item_details.
The hurdle, however, is the fact that another masterdata table is joined via a LEFT JOIN to the masterdata table that I want to aggregate; So the script_tab where this second table connected via LEFT JOIN is loaded is to the right of the one I would have to aggregate - but the GROUP BY clause necessary for any aggregation would necessarily include a field from the second table. I am unsure now as to the sequence in which the operations in the script will be executed: Ideally, of course, the JOIN should be there first so that I can access all the fields I need for the GROUP BY clause.
Can anyone clarify this?
Thanks a lot!