Unable to Connect

[opticshrew2]

Morning all,

I've creating a Power BI report that connects to the Common Data Service (CDS). When querying the CDS using this URL, "https://<tenant removed>.crm4.dynamics.com" I get the following error:

"The feed's metadata document appears to be invalid. Error: The type Microsoft.Dynamics.CRM.contact has conflicting definitions for the property <property removed>"

I've gone into the CDS and located the fields "Manager" (both with the same display name). I have since renamed one to "ManagerName" and the other remains as "Manager".

Any idea why this issue would still be occuring, is there something else I need to do?

Thanks,

J

[v-siky-msft]

Hi @opticshrew2 ,

Do you want to connect Dynamics 365 instance to Power BI?  Maybe you should post this post on PowerBI and D365 Forum.

I find some related threads, hope these can help.

https://social.technet.microsoft.com/Forums/en-US/b1829d0c-2b65-4ca3-a128-50323a91051b/odata-the-fee...

https://community.powerbi.com/t5/Service/Dynamics-365-to-Power-BI-Appsource-Metadata-Error/m-p/46550...

https://community.powerbi.com/t5/Desktop/Odata-Error-The-Feed-s-metadata-document-appears-to-be-inva...

https://community.powerbi.com/t5/Desktop/OData-The-feed-s-metadata-document-appears-to-be-invalid-qu...

Best  regards,

Sik

[DavidJennaway]

You may still have issues with fields called Manager and ManagerName, as CDS generates virtual fields by adding 'Name' as a suffix for lookups and option sets. Try renaming 'ManagerName' to something else to see if that's the issue

[opticshrew2]

Hi @v-siky-msft,

We're trying to connec to the Common Data Service using Power BI. However I think the issue sits within the CDS, reason being, we recently upgrades from Dynamics 365 v8.2 to v9.1. I reckon, doing so caused changes to the CDS.

I'm hoping that I come across others with the same error who ideally found a workaround.

Thanks,

J

[opticshrew2]

Hi @DavidJennaway,

We have a relationship and field both named <placeholder>_manager.

Is that likely to cause the issue?

Thanks,

J

[SERGIOD]

hI @opticshrew2 

Just wondering if you were able to resolve this issue you reported and if so, how did you go about it?

Cheers and thanks

Sergio

[opticshrew2]

Hi @SERGIOD ,

We recently went through a clean-up and now no longer experience this issue.

It could have been the issued stated above however I have no way of testing this.

Apologies