Anyone having issues with Power BI lineage not working consistantly? We have had 2 years of problems, that we are stuggling with getting lineage to work with Power BI. Would love to hear others experience with it. Below is latest issue and workaround. Issue Summary The lineage issue is caused by a mismatch between the Power Query Analyzer’s static analysis and the script’s dynamic column renaming approach. The Analyzer requires all information to be static, but the script dynamically generates its renaming map at runtime. This results in an incomplete lineage map with mismatched source and target column names. Workaround The recommended approach is to refactor the dynamic rename operation into a static, explicit mapping. This aligns the script with the Analyzer’s expectations and ensures accurate lineage. Current Dynamic Implementation (causes mismatch): #"Renamed Dynamically" = Table.RenameColumns(Source, List.Transform(Table.ColumnNames(Source), each Text.Proper(Text.Replace(_, "_", " "))) ) Proposed Static Implementation (aligns with Analyzer): #"Renamed Manually" = Table.RenameColumns(Source, { {"PROCEDURE_CODE", "Procedure Code"}, {"PROCEDURE_DESCRIPTION", "Procedure Description"}, {"CDT_PROCEDURE_CATEGORY", "Cdt Procedure Category"} // ...etc., for all required columns }) By using this static approach, the column renaming will remain consistent and correctly interpreted by the Analyzer.