Forum Discussion

Stan_Ogden's avatar
Stan_Ogden
New Member
9 years ago

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 Anal...
Need Help
Anonymous's avatar
Anonymous
Not applicable
9 years ago

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

  • JukkaN's avatar
    JukkaN
    Regular Visitor
    9 years ago

    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's avatar
      TePe
      Icon for Helper IV rankHelper IV
      9 years ago

      Same problem on my side... Looking urgently for a solution...

  • Ubon's avatar
    Ubon
    Frequent Visitor
    9 years ago

    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_Ogden's avatar
      Stan_Ogden
      New Member
      9 years ago

      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.

       

      • Ubon's avatar
        Ubon
        Frequent Visitor
        9 years ago

        Stan_Ogden

         

        I've worked around it by removing the fetchxml from my query.  We don't have that many account records in the database and don't have a requirement to limit the number of account records returned to only those with opportunities modified in last 365 days.  I'd like to know if I can use fetchxml in other queries though.

         

        Did your colleague take the same approach, or were did they amend the fetchxml?  If they fixed the fetch, would you be able to share the xml?