Keep in the mind the following best practices to make the most of the OneStream Connector:
-
Load only the necessary grain of data. Meaning, if you only need aggregated data at the month level, don’t load data at the daily level. While Power BI can handle hundreds of millions of rows, if not more, the smaller the model, the more performant it will be.
-
Limit the number of transformations you make. The more complicated the query, the higher chance there is for the query to fail.
-
Leverage OneStream’s financial logic, Cube Views, and Data Adapters to create the tables that will then be loaded into Power BI.
Example: Consolidations involve the parent entity only taking 40% of one of the child entities’ values. Ensure that this logic is done in OneStream, and you load the data adapter in Power BI which already has the values populated. Replicating the logic in Power BI is inefficient and would be better performed in the source system.
-
When providing All for ScenarioType, the results will return the ScenarioType of default that has been configured in OneStream.
