Problem "Sorry, we couldn't find column 127 in the table"

[lyly75]

HI

i hope you re doing well. i have probleme Power query in connecting severals tables  but it said that impossible to upload because of the change name of le columns 127"; i want it to ignore the problem because the column titles change every 6 months but I want it to compile them anyway, if you have idea?

[v-veshwara-msft]

Hi @lyly75 ,

Thanks for sharing the issue in Microsoft Fabric Community, and thanks to @Nasif_Azam and @Demert  for the helpful inputs already shared.

As already mentioned, this issue typically comes up when a query step is referencing a column that no longer exists or has a changed name. If the column names in your source change every 6 months, then hardcoding references like "Column127" can easily break the query.

You can update the query to handle such cases more dynamically. For example, using "Table.ColumnNames(Source)" will give you the list of current columns, and you can then process only those available. Also, wrapping column access logic in "try ... otherwise" will prevent the query from failing if a column is missing. This approach helps the query continue to load without interruption even if some expected columns are not present.

If you’re comfortable sharing  your M code or sample and a few example rows from your source, as @PwerQueryKees  suggested, it would help us provide more accurate guidance or reproduce the issue directly.

Hope this helps. Please reach out for further assistance.

If any of the responses already helped resolve the issue, feel free to mark it as the accepted solution so it’s easier for others to find.

Thanks.

[PwerQueryKees]

Please share:

• All your M-Code
  Not just the part you are struggling with, but also the part leading up to it. An error or issue often has its root cause earlier on.
• (a sample of) your data . Preferably not a screenshot (or at least an easy readable screenshot).
  So I can attempt to replicate your issues or question and possibly solve it quicker.
  
  

  Kees Stolker

  A big fan of Power Query and Excel

[Nasif_Azam]

Hey @lyly75 ,

I hope you're doing well too!

Regarding the issue you're facing with Power Query, it seems like the column names are changing, which is causing the error. Since the column names change every 6 months, I suggest using a more flexible approach that doesn't rely on static column names. Try these solutions:

1. Dynamic Column Names: You can try modifying your query to dynamically reference the columns. Instead of directly specifying the column name in Power Query, you can use the Table.ColumnNames() function to get a list of column names and then apply logic based on that. This way, even if the column names change, the query will still work.

   Example:

   let
       Source = YourSourceHere,
       ColumnNames = Table.ColumnNames(Source),
       // Further steps depending on column names
   in
       Source

2. Column Name Validation: Before applying transformations, you can use conditional logic in Power Query to check if the required columns are present and handle the situation gracefully. If the column doesn't exist, you can either skip or add a placeholder.

3. Ignore Errors in Loading: You could also suppress errors related to missing or renamed columns by using try ... otherwise statements, allowing the query to load without failing when a column is missing or renamed.

If you found this solution helpful, please consider accepting it and giving it a kudos (Like) it’s greatly appreciated and helps others find the solution more easily.

Best Regards,
Nasif Azam

[Demert]

Hi @lyly75  you would need to check your Power M Query steps in the advanced editor or in the query settings view. And look where you reference "column 127" and remove the step or the reference to "column 127" to resolve this error.