Forum Discussion
Report Refresh Error (msdyn mobileapp)
Hi,
My reports have been refreshing every night for several years without any problems until today, this is the error message I get:
I'm not very technical and so I hope the fix is easy and straightforward, can anybody shed some light on why this has happened and how to fix it please?
Thank you!
11 Replies
- DataVitalizer
Super User
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 💡 - DaniyalKhaleel1New Member
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
- ArchStanton
Power Participant
Thanks, I've passed this onto our IT department who are still digging into what to do
- EvgeniAb
Advocate I
Hi,
what changes do you apply to duplicated/conflicting relationship definition in the solution?
I though we cannot change anything in it as it's Microsoft managed solution.- ArchStanton
Power Participant
Thank you so much for sharing all this, I will pass it onto our IT team.
I'm not able to answer your question as all this is sitting with our IT department. I am due a call with them later and if I can find out anything relevant I'll share it with you.
You mention that the manual refresh should be manually reactivated? Are you saying that If I manually reschedule the refresh then there's a chance it might work again?
- EvgeniAb
Advocate I
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. - EvgeniAb
Advocate I
Refer to this issue when creating a ticket
https://admin.powerplatform.microsoft.com/support/knownissues/6697187
- ArchStanton
Power Participant
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 - DataMaster888New Member
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?
- ArchStanton
Power Participant
I've passed the information that EvgeniAb gave me to my IT department and have a follow up call in an hour to find out the latest.
I'm surprised at how few posts there are about this issue - Microsoft have really dropped the ball here, looks like my organisation with be without up to date MI for at least 2 whole days if not more- Fernando23New Member
Same thing here, no update for our dashboards because of this problem. If anyone finds a solution, please let us know.