Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!Learn from the best! Meet the four finalists headed to the FINALS of the Power BI Dataviz World Championships! Register now
What is up with building a model view and having the tables explode, like a thousand miles away from each other in the model viewer? What the hell is up with that?
The Cause:
Power BI's "auto-layout" algorithm is trying to avoid crossing relationship lines. When it gets confused by a complex schema, it "panics" and dumps the new table at an arbitrary coordinate (often 0,0), usually far away from where you are currently looking.
The Fixes:
* Collapse All (Ctrl + 1): Shrinks all tables to headers only. That "1000-mile" gap becomes a 2-inch gap, making it easy to drag the table back.
* Use Layout Tabs: Stop working in the "All Tables" view. Click the + at the bottom to create a specific layout (e.g., "Sales Schema") and drag in only the tables you need. These views don't explode.
This is supposed to be a mature product. Get your stuff together and don't like stuff like this happen going forward. It's completely ridiculous. What the hell?
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
Check out the February 2026 Power BI update to learn about new features.
| User | Count |
|---|---|
| 61 | |
| 54 | |
| 39 | |
| 16 | |
| 14 |
| User | Count |
|---|---|
| 98 | |
| 84 | |
| 35 | |
| 30 | |
| 25 |