Error

[dmonzon]

Hi.

I have this error.

Error del origen de datos: Expression.Error: The OData connector failed with the following error: We cannot convert the value null to type Record... . The exception was raised by the IDbCommand interface. Table: HistLinIntervencionQUERYsoloRecursosYreparaciones.
URI de clúster: WABI-WEST-EUROPE-D-PRIMARY-redirect.analysis.windows.net
Identificador de actividad: 6a341cbd-75f1-4193-8b44-9d823046751f
Identificador de la solicitud: a4aac063-2e75-4a23-acfa-6158d3e2547f
Hora: 2024-09-09 09:23:11Z

Thanks.

[Idrissshatila]

@dmonzon @Shivu-2000 

I opened an issue with microsoft support to investigate it, you can follow the issue in the link to know the latest update regarding this issue
https://community.fabric.microsoft.com/t5/Issues/The-OData-connector-failed-with-the-following-error...

[dmonzon]

All updates are failing. It's chaos.

[Idrissshatila]

Hello @dmonzon ,

I faced the same issue today, while the report was running normally for months.

[dmonzon]

Well... I've put this one up but I've actually had several reports that suddenly failed today that worked perfectly. On Desktop Ok and when I post Error

[dmonzon]

Thank you for your quick response. But when I update in PowerbiDesktop I don't have any errors. I only have it when I post it.

[Idrissshatila]

yes @dmonzon , the error is showing only on power bi service.

[dmonzon]

I have changed the 4 parameter in the BC connector and it works correctly as the video says it puts in the Reddit solution. But this is unacceptable..... it must be automated by PowerBi as managers do not understand this 😞

[Shivu-2000]

Hi @dmonzon 
The error indicates that Power BI is trying to convert a null value to a complex data structure (a Record) for a table named "HistLinIntervencionQUERYsoloRecursosYreparaciones."

Following could be work arounds available.

• Identify the Null Value:

  • Investigate Data Model: Look at your Power BI data model for the "HistLinIntervencionQUERYsoloRecursosYreparaciones" table. Identify the specific field causing the null value issue.
  • Examine OData Schema: Check the OData service schema to determine if the problematic field is marked as required.

• Address the Null Value:

  • Modify OData Service (if possible): If the field is optional in the OData service, modify the service to return a default value instead of null for that field.
  • Handle nulls in Power BI: Update your data model to handle null values gracefully. Options include:
    • Using conditional logic in DAX formulas to account for nulls.
    • Creating a separate "null flag" field to indicate the presence of null values.

• Verify Data Type Mapping:

  • Compare Data Types: Ensure that the data types in your Power BI data model accurately reflect the data types in the OData service.
  • Adjust Mappings: If mappings are incorrect, adjust them in Power BI to ensure compatibility.

If these aren't helpful, can you provide the sample data.

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Happy to help!