We've captured the moments from FabCon & SQLCon that everyone is talking about, and we are bringing them to the community, live and on-demand. Starts on April 14th. 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?
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 |
|---|---|
| 54 | |
| 39 | |
| 32 | |
| 17 | |
| 15 |
| User | Count |
|---|---|
| 64 | |
| 63 | |
| 37 | |
| 36 | |
| 22 |