Dynamics Community Forum Thread Details

Where should major transformations be done for Pbi embedded in D365?

We are customizing one of the out of box report from D365 F&O (CFO overview)
Our development team created a new workspace and published version 1 (V1) of report where new tables were connected.
Then our internal team worked on the V1 Pbix desktop file, cleaned up data model. All of transformations were done in a sql statement (these transformations includes joining tables, selected columns, filters, renaming), which we can view in the power query source. Pages and visuals were also updated significantly.

After that when the development published version 2 report in same workspace, the report did not update and continued to display Version 1 in D365 workspace.
So developer, created a copy of AX resource, used that while deploying to LCS. This seemed to have worked as Version 2 file is published successfully.

What I want to know is how to verify if the sql statement in native query is what could have possibly resulted in issue where the report didn’t update to version 2 in D365 workspace?

Also, what are the best ways to do transformations to pbi report which will be embedded in D365 since Direct Query has a lot of performance issues and we can’t due heavy transformation in PQ (such as joining tables, removing columns etc).

Should we create a view or continue to do sql statement for transformations?
We will be creating more Pbi reports to embed in D365. So, we are looking to find best way possible. Our internal team can create sql queries.
I am including the screenshot of data models to give you all an idea of how large of data model was in version 1 vs version 2 post clean-up.

Quick Links

Leaderboard