This is best Fabric, Power BI, SQL and AI community event. How do we know? The last event sold out! Save €200 with code FABCMTY200.
Register nowA new Data Days event is coming soon! This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. Don't miss out.
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?
Check out the May 2026 Power BI update to learn about new features.
Sign up to receive a private message when registration opens and key events begin.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
| User | Count |
|---|---|
| 28 | |
| 26 | |
| 25 | |
| 22 | |
| 13 |
| User | Count |
|---|---|
| 59 | |
| 50 | |
| 25 | |
| 20 | |
| 20 |