Forum Discussion
Non-existent phantom "Column" column causing circular references
I recently tried copy-pasting a calculated column to make a secondary column with minor differences to the first, but the moment I pasted PBI had a hickup and decided I had created a Column-named column.
I exited the report and reopened it, and verified that no such "Column" column existed, but when I tried creating the calculated column again I got the following error.
The first and last items are exactly the same and the Column is allegedly in the same table. But no such column exists.
Even if I search for column names across all tables, there is no column named "Column", yet it is apparently causing a non-existent circular dependency.
Is there a way to resolve this?
EDIT: I have tried restarting PBI and creating a whole new column, ending in "2", and here is what happens when I just try to close the whole report:
All three of these are in the same Table and there is no circular dependancy between them.
Hi SevsBo ,
It looks like Power BI has encountered a phantom circular dependency, likely due to internal metadata corruption or a hidden column reference. First, check for hidden columns using DAX Studio or Tabular Editor. You can run the following query in DAX Studio to list all columns in your model:
SELECT * FROM INFORMATION_SCHEMA.COLUMNSIf a column named "Column" exists, even if it’s not visible in the Fields pane, it might be interfering with your calculated column. Instead of copy-pasting, manually create the new calculated column with a slightly modified name, such as _ACV_Test instead of _ACV_2, and use VAR inside your formula to minimize dependency chains.
Try refreshing the entire report using Ctrl + Alt + F5, then save it under a different name and attempt to create the column again. Sometimes, relationships between tables can create an indirect circular dependency. Check the Model View and temporarily remove relationships involving your table, then try adding the column once more.
Clearing Power BI's cache can also help, as old column metadata might be causing the issue. Go to File > Options and settings > Options, then under Global, select Data Load and click Clear Cache. Restart Power BI afterward.
If the issue persists, consider moving the calculated column logic to Power Query instead of using DAX, as Power Query processes data before it enters the model, avoiding circular dependency issues. If none of these steps work, you may need to remove the table from Power BI entirely, re-import it, and then recreate the calculated column.
Let me know if any of these solutions help!
Best regards,
2 Replies
Hi SevsBo ,
It looks like Power BI has encountered a phantom circular dependency, likely due to internal metadata corruption or a hidden column reference. First, check for hidden columns using DAX Studio or Tabular Editor. You can run the following query in DAX Studio to list all columns in your model:
SELECT * FROM INFORMATION_SCHEMA.COLUMNSIf a column named "Column" exists, even if it’s not visible in the Fields pane, it might be interfering with your calculated column. Instead of copy-pasting, manually create the new calculated column with a slightly modified name, such as _ACV_Test instead of _ACV_2, and use VAR inside your formula to minimize dependency chains.
Try refreshing the entire report using Ctrl + Alt + F5, then save it under a different name and attempt to create the column again. Sometimes, relationships between tables can create an indirect circular dependency. Check the Model View and temporarily remove relationships involving your table, then try adding the column once more.
Clearing Power BI's cache can also help, as old column metadata might be causing the issue. Go to File > Options and settings > Options, then under Global, select Data Load and click Clear Cache. Restart Power BI afterward.
If the issue persists, consider moving the calculated column logic to Power Query instead of using DAX, as Power Query processes data before it enters the model, avoiding circular dependency issues. If none of these steps work, you may need to remove the table from Power BI entirely, re-import it, and then recreate the calculated column.
Let me know if any of these solutions help!
Best regards,
Thanks, DataNinja777!
I first tried to clear the cache but this did not solve the problem by itself. However I then deleted the relationships to the offending table and saved the report under a different name, and now it's back to normal! I have renamed it back to original, reinstated the relationships and it works like a charm. Thanks for your help!
