A value was encountered that has a type name that is incompatible with the metadata

[DanielMunoz]

I have an issue when updating Power BI reports starting from 01/24/2025. Data source error: OData: A value was encountered that has a type name that is incompatible with the metadata. The value specified its type as 'Edm.String', but the type specified in the metadata is 'Edm.Binary'. The exception was raised by the IDataReader interface. Please review the error message and provider documentation for further information and corrective action. Table: sng_ordendetrabajos.
Cluster URI: WABI-WEST-EUROPE-redirect.analysis.windows.net
Activity ID: e97a664b-5cc9-4e6b-b9cb-0e77e32a8732
Request ID: ba58aed6-2ee8-cda4-aef1-659f8068752c
Time: 2025-01-28 08:53:16Z

This error only occurs if the table has a field of type file or image.

[v-veshwara-msft]

Hi @DanielMunoz ,
We wanted to follow-up again to check if the issue has been resolved. If yes, please mark the helpful reply as 'Accept as solution'. This will help other community members with similar queries find a solution more quickly.
Thank you.

[scotech]

One of our clients has had the same issue, only affecting one specific entity being accessed via the Dataverse Web API for a couple of weeks now. On investigating, it does appear to be a problem with the OData service, which seems to be generating an incorrect CDSL metadata document. This then results in the type mismatch error observed. We've reported it to Microsoft support, who've confirmed they've passed the issue to the product team for investigation. I'll update this thread when I hear back from them regarding this.

[v-veshwara-msft]

Hi @DanielMunoz ,

We just wanted to check in again regarding your issue. If you’ve found a solution, marking the reply as the solution and leaving a kudos would be greatly appreciated, it helps the community and others with similar questions.

If you’re still facing challenges or have further questions, please let us know.

Thank you.

[nickdewitt · Accepted solution]

I had this same problem, looks like it started around 24th Jan.

I found it was related to the odata connection using the v8.0 api for dynamics, trying to load the accounts table from sales hub.

I swapped out the Power Query odata script in the advanced editor for a dataverse one and it worked ok.

let
Source = OData.Feed("https://xxx.crmx.dynamics.com/api/data/v8.0"),
accounts_table = Source{[Name="accounts",Signature="table"]}[Data]
in
accounts_table

 ->

let
    Source = CommonDataService.Database("xxx.crmx.dynamics.com"),
    dbo_account = Source{[Schema="dbo",Item="account"]}[Data]
in
    dbo_account

[v-kpoloju-msft]

Hi @DanielMunoz,

Thank you for reaching out to the Microsoft Fabric Community Forum.

We really apologies for the inconvenience, after reviewing the issue of a value was encountered that has a type of name that is incompatible with the metadata, here are few steps to may resolve the issue.

• Please ensure that the metadata for the OData service is accurately defined. It may be necessary to directly access the OData service to review the data types specified for each field. Verify that the field sng_ordendetrabajos is defined as Edm.Binary in the metadata.
• Refreshing the dataset in power bi can resolve issues. Navigate to the dataset settings and initiate a refresh. Additionally, clear the Power BI cache to avoid using outdated metadata by accessing the options menu and selecting the appropriate cache settings.
• In power bi, go to the model view and verify the data type of the field in question. Ensure it is set to Binary as expected. If needed, you can adjust the data type in power query to match the expected type.
• Please review the queries used to retrieve data from the OData source. Ensure they are not inadvertently converting binary data to string format. If the field undergoes any manipulation, such as concatenation or transformation, verify that these operations preserve the binary format.
• Please verify if there have been any recent modifications to the OData source or the database schema that might have impacted the data types. Please ensure that your Power BI Desktop or service is updated, as updates often include bug fixes and enhancements related to data connections.
•  

If this post helps, then please give us ‘Kudos’ and consider Accept it as a solution to help the other members find it more quickly.

Thankyou.

[v-kpoloju-msft]

Hi @DanielMunoz,

May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will help other community members with similar problems find a solution more quickly.

Thankyou.

[v-veshwara-msft]

Hi @DanielMunoz ,
Thanks for posting in Microsoft Fabric Community,

The error occurs because Power BI is receiving a field as Edm.String, while the metadata defines it as Edm.Binary. This typically happens when a file or image field is involved.

Recommended Actions:

1. Check for Recent Changes in the OData Source – If this issue started on January 24, 2025, verify if there was a schema update affecting data types.
2. Convert Data Type in Power Query – If a column is incorrectly interpreted, try conversion using Binary.FromText(_).
3. Exclude the Problematic Column – If a file or image field is not required for reporting, removing it may resolve the issue.
   
   

Please review these options.
Hope this helps.
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly and a kudos would be appreciated.

Best Regards,
Vinay Kumar.

[AlainDus]

Yep, removing the affected column resolves the issue.