Replies: 1 comment
-
It's deploying now. With my fiddling (don't know PowerBI) I changed the datasource to "localhost,AxDW". I changed them all to "., AxDW" and created another build and upgrade the sandbox environment and now it deploys. Can somebody just answer my question regarding the Power BI version compatible with Dynamics 365 F&O. I tried to google and but only found a document that said that D365F&O does not support the latest Power BI update and to find out which one is compatible. But where do I find this information or is this not relevant anymore? It apparently was still relevant in 2022 because that is what our Microsoft partner told us as well. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
We have a custom Power BI report, Inventory Value, that is embedded. So it is called from a menu item using a form and a controller that extends from PBIReportControllerBase.
This report used to work and then it failed to open the menu item.
My previous co-worker saved it then on a higher Power BI version according to the entry in Source Control.
We talked to our ISV partner and they said that D365F&O can only work with a certain version of Power BI. They indicated that Microsoft now deploys development environments with the correct version of Power BI. In Jan 2023 I redeployed my one Dev cloud-hosted environment and the Power BI version on it is March 2020. I recently deployed another cloud hosted environment and no Power BI was automatically installed.
So what version of Power BI does the embedded reports in D365F&O need?
I rolled back the PBIX-file to a changeset prior to it being saved against a higher PowerBI version.
There was also a problem with the entity store it used. I fixed the entity store and it refreshed without errors. I don't know much about PowerBI but did open the rolled back version in PowerBI and it draws the graphs correctly. I opened the Transform Data, and it first gave an error that the key doesn't corresponds with a column in the table. I clicked on 'Refresh' and it fixed that error. I saved the PBIX with a different name, I changed the resource to use the new PBIX and checked in the code and created a build and upgraded the sandbox with it. My Dev box is not linked to a PowerBI server so I cannot test on my Dev box. However after fixing the measurement, it uses in the entity store, I now don't get the error that it can't open the menu item. That part I could test on my Dev box.
For the new PBIX file, I uploaded it into LCS and then in D365F&O.
In the Entity Store I refreshed the changed measurement and I get the successful message: Measurement TMC_CostObjectStatementCache was deployed and populated successfully.
Then I went to Deploy Power BI Files and I still get the error message: Deployment failed for file Inventory Value V2.
I even logged out as myself, I have admin rights, and logged in as our Admin account that is the owner of the environment in LCS and it still can't deploy. We have other custom embedded PowerBI reports that was last changed in 2020 and they deploy successfully.
This Inventory Value report was also created in 2020 and it worked as I said. Something in its entity store measurement must have changed that gave the error that the menu item can't be opened and then it was opened and saved in a higher version of PowerBI.
Roling back to a 2020 version where it still worked should have put it in the correct version that D365F&O could work with correct?
How can I find out what is the reason why it fails to deploy? Any help is much appreciated.
Beta Was this translation helpful? Give feedback.
All reactions