Seems like these circular dependency issues can be unique snowflakes...but maybe you can help.
This problem is similar to a previous post of mine, so I'm going to reuse some wording here. But it's a new problem.
My data is from the real estate development industry.
Solved! Go to Solution.
this data looks like a natural hieriarchy to me. Have you considered denormalising the data into a single table?
Do you mean merging the three tables inside powerbi? Or creating that denormalized table on the server and then bringing it into PowerBi as a single table?
Reason I ask is that neither option is great for me at this point. Heres why:
Option 1: I have tried this before and the issue is that PowerBI has a tendency to generate many millions of extra rows so that it takes forever to refresh the data (and, truth be told, those three tables are actually already involving some joins of multiple tables on the inside PowerBI, which may be where the circular dependency is coming from...). This tends to make things pretty messy and confusing and prone to break. Partly my own limitations, admitadly.
Option 2: I work for a large busy organization with limited data engineering resources. It's hard for me to get that kind of table built and supported on our server because it means devoting engineer resources to it which don't report to me. If this is really the best option, than I could perhaps elevate this, but I'm trying to be self sufficient.
Is this making sense?
Ok, yes, I managed to get some engineering help to build a new view on Redshift which pre-joined the key data. Thank you. They used SQL to create the view. Haven't tried Power Query.
Check out new user group experience and if you are a leader please create your group!
On-demand access to all the great content presented by the product teams and community members! #MSBizAppsSummit #CommunityRocks
Check out how to claim yours today!