Report Refresh Error (msdyn mobileapp)

Hi ArchStanton​ 

The refresh failure is caused by a Dataverse metadata conflict: the msdyn_mobileapp table has two conflicting definitions for the msdyn_mobileappid property (OData error 10306) this is on the Dataverse/CRM side, not the report itself

I suggest checking Power Platform admin center/Service Health for any active incident, and Solution history for recent changes to msdyn_mobileapp

Did it work? 👍 A kudos would be appreciated
🟨 Mark it as a solution to help spread knowledge 💡

This error is from the Dynamics 365 CRM OData metadata, not Power BI itself.

The key error is:

msdyn_mobileappid_msdyn_mobileapp has conflicting definitions of the property msdyn_mobileappid_msdyn_mobileapp

Likely cause

The D365 environment has a duplicate/conflicting relationship or metadata definition for the msdyn_mobileapp table.

What to do

Open Power Apps → Solutions.

Check the msdyn_mobileapp table and its relationships.

Look for duplicate/conflicting relationship definitions involving msdyn_mobileappid_msdyn_mobileapp.

Publish all customizations.

If the issue remains, run Power Platform/D365 metadata validation or raise a Microsoft support ticket.

Since the refresh is failing at the OData metadata level, changing Power BI Import settings will not fix it

We are having the same issue since the 12th of September with datasets failing to refresh across multiple clients .
Error is:
DataSource.Error: The feed's metadata document appears to be invalid. Error: The type Microsoft.Dynamics.CRM.msdyn_mobileapp has conflicting definitions for the property msdyn_mobileappid_msdyn_mobileapp.

DataSourceKind = Cds | DataSourcePath = https://client.crm11.dynamics.com/ | Property = msdyn_mobileappid_msdyn_mobileapp

This happens if a dataset is connected to Dataverse using CDS connector. 
The error appears only on Dataverse were Mobile Apps Solution is present (installed 2 days ago).

It does not matter if you are using msdyn_mobileapp table or not - CDS checks the whole source scheme before even getting a table - if there is a bug - it throws the error
The issue is replicated on service and on desktop - clearing credentials does not help, removing the solution from Microsoft is not possible. 
Logged a ticket with MS - being redirected to Dataverse team - waiting for response.

**I had a call with MS support - they offer to run script to failing environments remotely (it worked for few that we tested)
But we need to give them 200+ PApps urls +OrgIDs to run the scrip manually) - not sure if we can do that.
Set aside the fact that refresh schedule should be manully re-activated.

Refer to this issue when creating a ticket

https://admin.powerplatform.microsoft.com/support/knownissues/6697187

Thanks, I spoke to our IT department and its something that they're investigating.
My organisation doesn't use the mobileapp so maybe removing it will fix the issue?

I'm surprised that other users haven't flooded the forum because this was a wholesale deployment / change that Microsoft made yesterday

Hi ArchStanton​ 

Thanks for posting the full error that screenshot explains it.

This is a Dataverse metadata conflict, not a problem with your report:

The type Microsoft.Dynamics.CRM.msdyn_mobileapp has conflicting definitions for the property msdyn_mobileappid_msdyn_mobileapp.

The refresh fails while Power BI reads the Dataverse metadata — before it ever reaches your data. That's why it makes no difference that your organisation doesn't use the mobile app table, and why others here hit it through the CDS connector too.

@EvgeniAb flagged Power Platform known issue 6697187: https://admin.powerplatform.microsoft.com/support/knownissues/6697187

That page needs an admin sign-in, so I can't confirm its status or timeline from here your Power Platform admin can check it under Support > Known issues. Since the conflict sits in Dataverse, the fix has to come from that side; there's nothing to change in Power BI.

A few things worth knowing:

1. Your admin should check the known issue and Service health, and if it's still active, raise a case from the Power Platform admin center quoting the issue ID, environment URL and org ID.
2. Don't rebuild the model or clear credentials — neither will help. @Serintek and @KevinAec, this especially applies to you: the refresh never reaches your tables, so your models are intact.
3. Editing or removing the Microsoft-managed solution isn't a viable workaround — managed components can't be edited directly, and customising around them creates dependencies that complicate later updates.
4. Once it's fixed, check whether your schedule needs switching back on Power BI disables scheduled refresh after four consecutive failures.

One general note: please don't send a .pbix to anyone, publicly or privately it usually contains cached data, queries and connection details. Keeping things in the public thread also means the advice gets peer-reviewed. No accusation intended toward anyone; it's guidance we give on every thread.

If anyone gets an update from their support case, please post it back here  it'll help the others.

Thanks,
C Srikanth
Community Support Team

Any update? I'm having the exact same issue with all of my dashboards since Sunday, was Microsoft able to respond to your ticket/resolve the issue on their end?

Same issue here, can't think of any work arounds to avoid spending weeks rebuilding queries and relationship tables. If only Microsoft can allow us to pull the original metadata column names.

A ticket has been logged with Microsoft by our IT dept, I'm hoping this gets resolved before month-end reporting. If this isn't fixed by then we are in trouble