Forum Discussion
Error al actualizar desde la web
Buenos días, he tenido este problema , y siempre que actualizo me sale el problema en diferente tabla, por lo que no sé que pueda estar pasando, entre las acciones ya realizadas para tratar de solucionar este error ha sido actualizar la puerta de enlace, desactivar el firewall, he observado los archivos de google sheets y sí se muestran en la web. Y también nos percatamos que desde que surgió este error si entramos al reporte no nos aparece la ultima fecha de actualización, no se si ha alguien le haya pasado lo mismo que nos pudiera compartir qué hicieron para resolver este problema
Error del origen de datos: {"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":"No se encontró la columna '' de la tabla."}},{"code":"DM_ErrorDetailNameCode_UnderlyingHResult","detail":{"type":1,"value":"-2147467259"}},{"code":"Microsoft.Data.Mashup.ErrorCode","detail":{"type":1,"value":"10224"}},{"code":"Microsoft.Data.Mashup.ValueError.Detail","detail":{"type":1,"value":""}},{"code":"Microsoft.Data.Mashup.ValueError.Reason","detail":{"type":1,"value":"Expression.Error"}}],"exceptionCulprit":1}}} Table: Metas.
URI de clúster: WABI-PAAS-1-SCUS-redirect.analysis.windows.net
Identificador de actividad: 697f9ebf-e968-4666-a783-c7945342ee58
Identificador de la solicitud: 8f9fc71f-a310-b5b7-7c89-94fa2c01e209
Hora: 2025-07-31 16:20:28Z
Hi prom2025 ,
If you're getting this error when refreshing from Google Sheets.Data source error: Table column '' not found.
It usually means a column expected by Power BI is missing, renamed, or misaligned in the source. Here's what worked for us.
- Open Power Query Editor → Find the table causing the error (check the error message for the table name).
- Review Applied Steps (especially Changed Type, Renamed Columns, or Removed Columns).
- Look for any step referencing a missing or blank column.
- Delete or adjust the step to match the current column names.
- Check your Google Sheet:
- Make sure the first row contains clean headers.
- Avoid blank rows, merged cells, or extra headers.
- Save and Close Power Query → Apply changes → Try refreshing again.
Regards,
Akhil.
5 Replies
Is your table structure static or do you frequently add or remove columns in your data sources?
Hi prom2025 ,
If you're getting this error when refreshing from Google Sheets.Data source error: Table column '' not found.
It usually means a column expected by Power BI is missing, renamed, or misaligned in the source. Here's what worked for us.
- Open Power Query Editor → Find the table causing the error (check the error message for the table name).
- Review Applied Steps (especially Changed Type, Renamed Columns, or Removed Columns).
- Look for any step referencing a missing or blank column.
- Delete or adjust the step to match the current column names.
- Check your Google Sheet:
- Make sure the first row contains clean headers.
- Avoid blank rows, merged cells, or extra headers.
- Save and Close Power Query → Apply changes → Try refreshing again.
Regards,
Akhil.Hi prom2025 ,
Just checking in were you able to resolve the refresh error from Google Sheets? The issue usually comes down to missing or renamed columns in the source or Power Query steps referencing outdated headers. If it’s still giving trouble after cleaning the headers and reviewing applied steps, feel free to share more details happy to help dig deepe.
Regards,
Akhil.Hi prom2025 ,
circling back were you able to track down what was causing the Google Sheets refresh error? If the header cleanup and step review didn’t resolve it, we might need to look at whether the sheet structure itself changed (like hidden rows/columns or merged cells). Let us know how far you got and we can help troubleshoot the next steps.
Regards,
Akhil.Hi prom2025 ,
I hope the response provided helped in resolving the issue. If you still have any questions, please let us know we are happy to address.
Regards,
Akhil.
