Microsoft Fabric Community Conference 2025, March 31 - April 2, Las Vegas, Nevada. Use code MSCUST for a $150 discount.
Register nowThe Power BI DataViz World Championships are on! With four chances to enter, you could win a spot in the LIVE Grand Finale in Las Vegas. Show off your skills.
Hi, i launch the following command to find dependency in DAX Studio and it no longer works. It worked before.
Anyone has an idea?
I check the measures, there is no "!" marks.
select * from $SYSTEM.DISCOVER_CALC_DEPENDENCY
Thanks to all.
Solved! Go to Solution.
So, finally i found out why it didn't work.
In M, i have a table from SQL Server and i add some custom columns to this table, which is ok, and i referenced this table to create another table. Untill here, tables are fine, it loads to the model, no error message.
However, when trying to do select * from $SYSTEM.DISCOVER_CALC_DEPENDENCY in DAX Studio, i got the error message.
Solution is to stop the referencing, just re-bring the table from SQL and do the rest.
well, I understand that, but we can't just stop referencing tables. we're using references to avoid using tables' duplication, otherwise the dataset file gets bigger for nothing. ther should be another way to fix the reference issue, having a reference shouldn't be an issue of bad reference when reading the metadata, don't you agree?
cheers
AG
So, finally i found out why it didn't work.
In M, i have a table from SQL Server and i add some custom columns to this table, which is ok, and i referenced this table to create another table. Untill here, tables are fine, it loads to the model, no error message.
However, when trying to do select * from $SYSTEM.DISCOVER_CALC_DEPENDENCY in DAX Studio, i got the error message.
Solution is to stop the referencing, just re-bring the table from SQL and do the rest.
Hey @danning1234 so your saying instead of referencing, just duplicate the query?
hi @Anonymous , according to my experience, yes.