Power Query Relationship Manager for Joins, Appends, and Query Dependencies
Add a relationship manager inside Power Query for Power BI that visually manages joins, appends, merges, and query dependencies.
Problem:
In larger Power BI models, many important data connections are created inside Power Query through merges, appends, and referenced queries. These relationships are often harder to manage than model relationships because they are spread across individual query steps.
This can make models more difficult to maintain, especially for areas like finance where data accuracy, traceability, and controlled transformations are critical.
Proposed Solution:
Create a Power Query Relationship Manager that allows report creators to:
- View all merges, appends, joins, references, and dependencies in one place.
- See which queries feed into other queries.
- Identify broken or risky query connections.
- Manage join types and append logic centrally.
- Document why specific joins or appends exist.
- Improve visibility over transformation logic before data reaches the model.
Benefits:
- Reduces memory and refresh inefficiencies.
- Improves model stability.
- Makes finance and operational models easier to audit.
- Reduces reliance on complex front-end measures.
- Helps prevent model breakdowns caused by hidden query dependencies.
- Improves development speed for large Power BI models.
Example:
A finance model may use multiple source tables for accounts payable, accounts receivable, inventory, payroll, and general ledger data.
Instead of tracking each merge or append inside separate query steps, the developer could open a Relationship Manager view and see how each query connects before the data is loaded into the model.
Business Impact:
This would make Power BI models easier to maintain, more reliable, and more scalable. It would be especially valuable for enterprise reporting, finance reporting, and large segmented models where many transformations happen before the data reaches the semantic model.
Recent ideas
Fabric Mirroring for Oracle fails on unconstrained NUMBER columns
Hi, might there be a way to Mirror Oracle database to Fabric when tabels include unconstrained NUMBER columns by setting preconditions for those as it common for Oracle databases? BR, MagnusMagnusBerglund9 hours agoNew MemberNew20Views0likes0CommentsEmbedded Power BI: allow 12/24-hour clock setting independent of formatLocale
Problem In Power BI embedded reports (app-owns-data, JavaScript SDK), localeSettings.formatLocale is the only way to influence date and time display. The hour cycle (12 or 24 hour) is tied to th...VijaySama5881 day agoNew MemberNew6Views0likes0CommentsAdd Initial Horizontal Scroll Position to Matrix and Table Visuals
Please add an option to Power BI Matrix and Table visuals that allows report developers to configure the initial horizontal scroll position when the visual loads. Suggested setting: Format visual >...Panteras011 day agoFrequent VisitorNew3Views0likes0CommentsFabric Mirroring (and all artifacts) - Reassign owner
Probelm: I have users who have created Mirroring from Azure SQL DB's (although this problem exists with all mirroring) and if they dont log into fabric often the mirroring breaks. While best prat...Jreed_74741 day agoNew MemberNew120Views1like1CommentPowerBI Forced Refresh after Report Deployments
Currently, when you make an update to a PowerBI report and deploy (click update app), it doesn't force a refresh for your end users. Thus, they end up getting error messages on their reports (dependi...kaitlyn_workman1 day agoRegular VisitorNew3Views1like0Comments