Earn the coveted Fabric Analytics Engineer certification. 100% off your exam for a limited time only!
Greetings.
Greetings,
Using Power BI Desktop - Version: 2.38.4491.282 64-bit (August, 2016)
Note: This issue also occurred in the prior version.
Connecting to a CRM 2015 Online Instance
ODATA FEED.
https://xxxxxxx.crm.dynamics.com/XRMServices/2011/OrganizationData.svc/
It connects and shows the Navigator screen with the available datasets.
A smaller dataset will load fine. A larger dataset ( AccountSet ) generates the following error.
Load : AccountSet Failed to save modifications to the server. Error returned: 'OLE DB or ODBC error:[Data Source.NotFound] OData: request failed (404): The remote server returned an error:(404) Not Found. (Not Found). '.
Solved! Go to Solution.
I used to get this same kind of error dealing with Leads in CRM. I solved it by pairing down a lot of the columns. I had initially just let it choose to bring in all columns and would get issues like that. Getting rid of a lot of the "fluff" solved it in my case.
OK ... I found a seperate / similar forum post that implied that this issue may be caused by the number of columns ( not rows ) that were being pulled into PowerBI desktop. So I reduce the number of columns using Remove Column option to limit the query. This allowed me to bring in and work with the Account Set.
Did you ever locate documentation stating what the column limitation is?
I have a customer experiencing the same problem as you, and I would like to know how many columns we need to cut out.
I used to get this same kind of error dealing with Leads in CRM. I solved it by pairing down a lot of the columns. I had initially just let it choose to bring in all columns and would get issues like that. Getting rid of a lot of the "fluff" solved it in my case.
User | Count |
---|---|
141 | |
113 | |
104 | |
77 | |
64 |
User | Count |
---|---|
135 | |
123 | |
101 | |
71 | |
61 |