Forum Discussion
Error importing data for Dynamics 365 sales content pack
Hi I have set up a new CRM and am working on the sandbox with the standard sample data
I have logged into the Power BI service and clicked get Data
then browsed to a content pack called "Sales Analytics for Dynamics 365" (I think this must be a renaming of the "Dynamics CRM Online Sales Manager" pack.
It asks me to authenticate and I select OAuth
I log in with my credentials.
It then says "importing data ...this may take a while"
After a few seconds it fails with the following message
Please try again later or contact support. If you contact support, please provide these details.
So i am left with a very empty report in my Power Bi service.
I should also point out that I am a bit of a Power Bi newbie but I think I am following the correct steps
14 Replies
- AnonymousNot applicable
How about you connect to the Dynamics CRM Online Sales Manager pack in Power BI Service?
Regards,
Lydia Zhang - dimitrievskiFrequent Visitor
It started happening today for me too, it was working perfectly for a week or so. No changes have been made both in CRM or in Power BI. I recreated it also thru Dynamics CRM Online Sales Manager pack and still the same error occurs.
Any thoughts?
- AnonymousNot applicable
Stan_Ogden dimitrievski,
The issue has been reported internally to Power BI team, I will post back once I get any updates.
Currently, you can use Power BI Desktop as a workaround to connect to Dynamics 365.
Regards,
Lydia Zhang- JukkaNRegular Visitor
My guess is that the Service Update 3 for Microsoft Dynamics CRM 8.2.1 which was deployed to our v8.2 Dynamics 365 instances on Friday broke the Power BI content packs. When testing either the Sales or Service content packs in a CRM org with 8.2.1.207 version the "Invalid XML" error appears. When I tried adding it on a v8.1 instance (8.1.1.1003) there wasn't any errors.
- TePe
Helper IV
Same problem on my side... Looking urgently for a solution...
- UbonFrequent Visitor
Anonymous
Hi Lydia
My error is when using Power BI Desktop (with May update) with the Sales Manager.pbix content pack.
Dynamics 365 online Version 1612 (8.2.1.207).
Fails on 'Accounts' query with:
DataSource.Error: OData: Request failed: The remote server returned an error: (500) Internal Server Error. (Invalid XML.)
Do you know if there is an updated content pack for this version of Dynamics 365 or if there is a correction available for the failing query?
- Stan_OgdenNew Member
In the end my learned colleague (who knows much more about this kind of thing than me) decided that the XML in the query for Accounts was bad. He fixed it.
I think MS have made a mistake and broken it when they have updated the pbix file.
- UbonFrequent Visitor
I think we have same issue following update to Dynamics 365 this weekend - (Version 1612 (8.2.1.207) (DB 8.2.1.207) online
Error on 'Account' query:
DataSource.Error: OData: Request failed: The remote server returned an error: (500) Internal Server Error. (Invalid XML.)
Details:
DataSourceKind=OData
DataSourcePath=........ - AnonymousNot applicable
Stan_Ogden,
While this post hits my exact issue right on the head, I am sorry but I'm still not clear exactly what your colleague did to correct the issue with the Account entity. It would be incredibly helpful if we knew what was copied from what table to correct this. Thank you.
- contismaNew Member
If you goto the query editor, right click on the Accounts query and select advanced editor.
In here you will see:
let Source = OData.Feed(CRMServiceUrl, null, [Concurrent = true, ODataVersion = 4, Query=[fetchXml="%3Cf......
The Query= section is what is now failing since the update.
Remove the
, Query=[fetchxml=.....]
so you end up with
let Source = OData.Feed(CRMServiceUrl, null, [Concurrent = true, ODataVersion = 4]), accounts_table = ......and this should fix the error.
A key piece of the query that is lost is the fetchxml was filtering to only accounts that had an opportunity that was modified in the last 365 days.
If you have the time to identify what is wrong with the fetch xml, I would be intrigued to know what should be in the "query" section.
- AnonymousNot applicable
Thank you contisma. Removing the fetchxml worked like a charm.