Hi there,
To address your problem, let's first understand how a Data Management (DM) step works for a custom calculation. A DM step processes data units in parallel. You pass information about the destination data unit on the left-hand side of the equation, so you cannot enter a data unit on the left-hand side without causing an error as those are read from the DM step itself. However, on the right-hand side, you can specify the source data units from which you want to pull data.
If you want to process all 4 entities from a single DM step, you can use "E#Parentof4EntitiesYouWantToCalculate.base" notation. This will enable you to include all the desired entities in a single step.
In the screenshot you shared, the time filter mentions "T#|WFYear|.base." This creates 12 separate steps, one for each month, and processes them Sequentially. Similarly, if you apply the same concept to entities, it will create six different DM steps, one for each entity, and process them in parallel. This only applies to data units not for account level dimensions.
For the "api.data.calculate" part, you can use filters to calculate for all UD1 members based on your filter for a single entity. The syntax would look like this:
api.Data.Calculate("LHS = RHS",,,,,"YourUD1Filter",,,,,,,,,,)
This filter will calculate for all UD1 members according to your specified filter for a single entity.
Please note that while this approach is simple and suitable for smaller calculations, it may not be the best practice for larger and more complex scenarios. In such cases, you might consider using databuffers to improve efficiency, but explaining that process here would be quite complex.
I hope this explanation helps. If you have any further questions or need additional assistance, please feel free to ask.
Thanks, Omkareshwar
Archetype Consulting
