Install update error, desktop updates correctly

[Syndicate_Admin]

Hello.

I have a report that when I update it in Desktop I don't have problems, but after publishing it, the scheduled updates in Fabric give me the following error:

Data source error: {"error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError","pbi.error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError","parameters":{},"details":[{"code":"DM_ErrorDetailNameCode_UnderlyingErrorCode","detail":{"type":1,"value":"-2147467259"}},{"code":"DM_ErrorDetailNameCode_UnderlyingErrorMessage","detail":{"type":1,"value":"Registry field 'DATOS_INTERLOCUTORES' was not found."}},{"code":"DM_ErrorDetailNameCode_ UnderlyingHResult","detail":{"type":1,"value":"-2147467259"}},{"code":"Microsoft.Data.Mashup.ErrorCode","detail":{"type":1,"value":"10071"}},{"code":"Microsoft.Data.Mashup.ValueError.Reason","detail":{"type":1,"value":"Expression.Error"}}],"exceptionCulprit":1}}} Table: F_BI_GUINE.
Cluster URI: WABI-WEST-EUROPE-B-PRIMARY-redirect.analysis.windows.net
Activity ID: 066c13e6-9aae-4d72-9ca9-b2e390a01533
Request ID: 657161a3-a1e3-33af-ae80-5e204a3d070b
Time: 2025-05-23 04:56:28Z

The error tells me that it does not find the DATOS_INTERLOCUTORES field, which originally exists and undergoes a series of transformations:

Let
Source = Odbc.DataSource("dsn=a_prd", [hierarchicalNavigation=true]),
A20_Schema = Source{[Name="A20",Kind="Schema"]}[Data],
F_BI_GUIN_View = A20_Schema{[Name="F_BI_GUIN",Kind="View"]}[Data],
#"Split column by delimiter" = Table.SplitColumn(F_BI_GUIN_View, "DATOS_INTERLOCUTORES", Splitter.SplitTextByDelimiter(";", QuoteStyle.Csv), {"DATOS_INTERLOCUTORES.1", "DATOS_INTERLOCUTORES.2", "DATOS_INTERLOCUTORES.3"}),
#"Changed type" = Table.TransformColumnTypes(#"Split column by delimiter",{{"DATOS_INTERLOCUTORES.1", type text}, {"DATOS_INTERLOCUTORES.2", type text}, {"DATOS_INTERLOCUTORES.3", type text}}),
#"Renamed Columns" = Table.RenameColumns(#"Changed Type",{{"DATOS_INTERLOCUTORES.1", "GUIN"}, {"DATOS_INTERLOCUTORES.2", "SUR_GUIN"}, {"DATOS_INTERLOCUTORES.3", "Other"}}),
#"Changed Type1" = Table.TransformColumnTypes(#"Renamed Columns",{{"FILE", Int64.Type}, {"DATE", type date}})
in
#"Changed type1"

The gateway is up-to-date and online, all other reports are updated correctly.

I've tried several things, but I don't understand why it failed in Fabric when updating, but not in Desktop.
Any ideas?

UPDATE

More reports begin to fail me, with the same reason and a different field from their respective tables.

{"code":"DM_ErrorDetailNameCode_UnderlyingErrorMessage","detail":{"type":1,"value":"The 'DATE' column of the table was not found."}},

[v-pgoloju]

Hi @Syndicate_Admin,

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

As we haven’t heard back from you and there are no further queries at this time, we’ll proceed to close this thread for now.
Should you need any additional assistance, please feel free to start a new thread we’re always happy to help.

Best regards,
Prasanna Kumar

[v-pgoloju]

Hi @Syndicate_Admin,

Just following up to see if the solution provided was helpful in resolving your issue. Please feel free to let us know if you need any further assistance.

If the response addressed your query, kindly mark it as Accepted Solution and click Yes if you found it helpful  this will benefit others in the community as well.

Best regards,

Prasanna Kumar

[v-pgoloju · Accepted solution]

Hi @Syndicate_Admin,

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

The recent update to the 64-bit Oracle Client 19c (version 19.27) is likely the cause of the increasing column-related errors during scheduled refreshes in Power BI Service. The newer driver may handle metadata exposure differently, causing the gateway to fail to detect certain columns that Power BI Desktop still recognizes due to cached data. Since the gateway relies on the Oracle client for data access, any issues with the driver can directly impact refresh functionality. To resolve this, you can either roll back to the previous Oracle client version that worked reliably or try reinstalling the current version to fix any configuration issues.

If the issue still persists, I’d recommend raising a support ticket with Microsoft. The support team can look into the backend and provide more in-depth assistance tailored to your environment.

https://learn.microsoft.com/en-us/power-bi/support/create-support-ticket

If this solution helped, please consider marking the response as accepted and giving it a thumbs-up so others can benefit as well.

Best regards,
Prasanna Kumar

[v-pgoloju]

Hi @Syndicate_Admin,

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

The error occurs because the DATOS_INTERLOCUTORES column is not always available or recognized during the refresh in Power BI Service, even though it works fine in Desktop. This is likely due to schema drift or inconsistencies in the source view. To resolve this, you should explicitly check if the column exists using Table.ColumnNames before performing any transformations. Wrapping your logic in a conditional check ensures that the column is only processed if present, preventing the gateway from failing. Additionally, avoid relying on dynamically changing views by creating a stable version with a fixed schema, and use Table.SelectColumns to define the expected structure clearly. 

If this solution helped, please consider marking the response as accepted and giving it a thumbs-up so others can benefit as well.

Best regards,
Prasanna Kumar

[Syndicate_Admin]

The problem is getting worse, as more reports begin to give this problem, each with a different column.
Just yesterday I updated the Oracle connector for this:

64-bit Oracle Client for Microsoft Tools 19c (version 19.27)
Since he told me that the one I had was obsolete. Could it be the problem?