Forum Discussion

desertislesql's avatar
desertislesql
Most Valuable Professional
11 years ago
Solved

Error trying to get data from Microsoft Dynamics CRM

We are trying to use the Power Query connection in Office 365 Excel to make an Odata feed connection to CRM.  There are about 200 fields we are trying to access.  After the fields are added, a window popus up in Excel is waiting for another application to complete an OLE Action.  Any help would be appreciated.

  • desertislesql's avatar
    desertislesql
    11 years ago

    There appears to be an error with the way that Microsoft Dynamics CRM was configured, which meant some of the embedded tables were pointing to nothing.  Removing all of those tables, which were not being used resolved the connection issue.  Tip: Make sure CRM is configured correctly as it can cause a Odata issues.

6 Replies

    • desertislesql's avatar
      desertislesql
      Most Valuable Professional

      I started with pulling in CRM data from customers and that worked fine.  Now trying to pull in Sales, which has many fields and has been problematic.  I need that data though, so I have to figure out how to make it work.

  • ashishrj's avatar
    ashishrj
    Power Participant

    desertislesql Try reinstalling updated version of Power Query and while importing data make sure that the bandwidth for internet connection is sufficient enough to pull such a huge amount of data from CRM Online. Finally if this doesn't works try installing Excel again. I have done projects pulling data from CRM but never faced such issue. 

    • desertislesql's avatar
      desertislesql
      Most Valuable Professional

      I'll try that.  The PC being used for this has 32 GB of ram and a 64 bit OS, so I didn't think it was a hardware issue.  Since CRM is in the cloud it could be the network. Hopefully your suggestion makes a difference.  I'll let you know how it works out.

      • desertislesql's avatar
        desertislesql
        Most Valuable Professional

        Latest versions of Power Query and Excell from office 365 made no difference.  Appears to be some sort of data issue in CRM, which is hosted in the cloud.  Still investigating the issue.