Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.

OData error with Dynamics CRM Online - No longer Sync

Hi, 

 

This issue is very similar to the problem we had last June 2018 that affected hundreds of customers.

 

data refresh/sync from PowerBI desktop works fine. No problems.

 

Published reports are unable to sync from Dynamics 365 Online using oData feed.

 

This has started for ALL my published reports on 21/10/2018 à 10:01:03 AM   EASTERN TIME.

 

Here is the error:

The feed's metadata document appears to be invalid. Error: The type Microsoft.Dynamics.CRM.EntityMetadata has conflicting definitions for the property Attributes.

 

 

Status: Needs Info
Comments
v-qiuyu-msft
Community Support

Hi @PhilippeAllard,

 

On Power bi service, please go to Refresh History, find the failure refresh record, click Show button it will display RequestID, Cluster and Time information. Please share the error message with these detail information with us. 

 

Best Regards,
Qiuyun Yu 

v-qiuyu-msft
Community Support
Status changed to: Needs Info
 
PhilippeAllard
New Member

Hi, 

 

turned out I have opened a support case for this... here is the info you requested but make sure you guys are not working double on the same issue.

 

Message:The feed's metadata document appears to be invalid. Error: The type Microsoft.Dynamics.CRM.EntityMetadata has conflicting definitions for the property Attributes. Table: opportunities (2).
Cluster URI:WABI-CANADA-CENTRAL-redirect.analysis.windows.net
Activity ID:2241788b-72f1-44c0-b8db-96ff1f8da82b
Request ID:662ab64e-c972-4d08-a9c2-518f877d321e
Time:2018-10-22 19:10:21Z

 

v-qiuyu-msft
Community Support

Hi @PhilippeAllard,

 

Thank you for your prompt. As you already created a support ticket, please follow up with case owner to resolve the issue. It would be better if you could share the solution once you resolve the issue. 

 

Best Regards,
Qiuyun Yu