Power Query: The Fix You Need Now

Key insights

• The video highlights a fix for Power Query’s Changed Type step, which uses Table.TransformColumnTypes and hard-codes column names.
  That hard-coding can break queries when column names change, and Microsoft released a fix around May 2025 that was not obvious to find.
• The presenter demonstrates a MissingField error tied to the Culture argument during type conversion.
  This error shows how small argument or name mismatches can stop a refresh.
• For immediate recovery, update Office, run a Quick Repair, and clear Power Query caches.
  If needed, enable Power Query diagnostics tracing to inspect logs and find the root cause.
• A separate regression in August 2025 was tied to the Analysis Services engine and was reported fixed in Build 20222.
  A common community workaround for that regression was temporarily turning off the Grand Total for rows and columns to allow refreshes.
• Follow Microsoft guidance on authentication and connectors: connectors handle sign-in and credentials stay in local or service stores, not inside M code.
  Use the documented Web connector flow (Web page or Web API with supported auth) instead of embedding secrets in queries.
• Practical recommendations: keep Office updated, test Table.TransformColumnTypes after any column name change, and avoid storing secrets in workbooks or M code.
  Monitor diagnostics and use supported connectors to reduce refresh failures and security risk.

Keywords

secret power query fix, power query fix, power query troubleshooting, power query performance fix, excel power query error fix, power query refresh issue fix, power query M code troubleshooting, optimize power query performance