Don't miss your chance to take the Fabric Data Engineer (DP-700) exam on us!
Learn moreThe FabCon + SQLCon recap series starts April 14th at 8am Pacific. If you’re tracking where AI is going inside Fabric, this first session is a can't miss. Register now
I have custom column which works perfectly. When I copy the table and copy the same custom column (with the relevant parts of the formula changed to reference the new table) it says there is a circular dependency. To be clear, the new table is identical to the old one, but is simply connecting to a new instance of Salesforce.
So my question is why does a custom column work perfectly with one table, and then has an error when doing exact the same thing in a n exact copy of the table?
To be fair, PBI was trying to ask me to report this as an error, so I guess it's just another example of how amazing PBI is...
@Anonymous , Copy of the formula, should not give a circular error. But when you are using tablename<column name>, it might be referring to another table, which you can not do directly.
https://www.sqlbi.com/articles/avoiding-circular-dependency-errors-in-dax/
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
| User | Count |
|---|---|
| 53 | |
| 40 | |
| 38 | |
| 19 | |
| 18 |
| User | Count |
|---|---|
| 70 | |
| 69 | |
| 34 | |
| 33 | |
| 30 |