Hit Reply and let us know what you think of the new model view UI. To learn more about this feature, please visit our blog.
Here are some areas that we'd like to hear about in particular:
Thanks and we look forward to hearing your feedback!
- The Power BI Model View Team
Trash my table relationships view without warning and with no recourse?? Absurd and ridiculous. For performance reasons? Heck, just delete my data model and all the data. Zero results with zero latency. Perfect performance. Bonuses all 'round.
And I get to spend my time searching on how to correct this absurdity and then more time trying to rebuild the relationships in a year-old data model with quite a few tables. All because I dared to add a new table using the "latest" PBI Desktop release.
Can you tell that I'm not pleased with this "enhancement." "Auto Detect" was useless. I have to rebuild all the table relationships manually? Really. Whoever came up with this as an "improvement" should be ashamed.
So the Evironment Variable setting appears to work an restore functionality. I would recommend in the future "enhancements" that you make the "old" system the default, and have any "new" features like this require effort on the part of the user to enable the feature whenever the "new" feature disables existing functionality. I'm back online sooner than I expected, but the disruption was a disruption of flow and productivity nonetheless.
Thank you for the opportunity to provide feedback on the new model view UI. I have been a Business Intelligence consultant for a few (15) years, so hopefully my input will add value.
For a given table in the schema view:
Add formatting to make the visual quicker to interpret:
Ability to sort Folders by ordinal position (Customer is more significant than a Bin).
Ability to sort Fields by ordinal position not alphabetical (Start Date displays before End Date).
Keep the Property -> Advanced Group open when selecting other fields.
In the Property for field, show the fully qualified source field (Ex. Target: Shipment Number <-- Source: erpdb.oper.shpnbr)
Make Reference Tables (i.e. Role Based Dimensions) obvious as well as include the table that it references. Maybe a light grey background or grey font.
Ability to create a relationship using a "BETWEEN" relationship. For example I have a Inventory Stock Level of 100 units starting on 1/10 until 1/14. On 1/15 I receive a shipment of 50 units. I cannot create a relationship that states Calendar Date BETWEEN Inventory Level Start Date and Inventory End Date. Gotta do that, but supporting complicated DAX or M-Query adds an unnecessary level of complexity.
The ability to create filters as fields. For example if I only want Active Customers, I can create a Filter object that drags to the filters not visual to limit results. So if I only want to see Active Customer, I can create a filter field that does this. This is valueable for creating complex DAX objects out of the box so that end users don't have to learn DAX.
The ability to export the model view metadata to CSV, JSON, or Excel.
Predefined Metadata Fields
Add Perspectives. Selecting a perspective highlights the tables in that perspective. Selecting multiple perspectives highlights all the tables in those perspectives.
Create a Lineage View. We know that the organization in the source is technology driven, while the organization in the semantic model is business driven. There is not a 1:1 match from table -> folder and column -> field. A lineage view would show the transformations used to get from the source to the target. (Steal it from Power Query -> Query Dependencies or the dataflow view). This should include Aggregations in the lineage.
Leverage the empty space in the bottom status bar to tell me about my model:
@Ole111 - What did you set the value to? it must be set to an integer between 10 and 1000. I would very strongly discourage setting it higher than 100 though. If you have more tables in your model than that number, the All Tables layout will be disabled.
I have the same gripes as others. Removing the All Tables view without an easy button "Enable All Tables" and having the Model Diagram re-appear just as we have had it, meticulously ordered and structured so that we have a clear diagrammatic view of everything... I have to say...
FYI creating a new layout, CTRL ALT dragging everything onto the canvas and re-ordering everything just doesn't cut it. No longer can we have new tables automatically appear on the canvas, which means there is that overhead of periodically having to check that all tables are actually on the canvas, especially when you open up a report that another person has developed....
If I select my table in the Model view, I can't switch the storage mode from DQ to dual. The option is not visibile in the properties of the table.
Is there a solution for this ?
Please please bring the All tables View back.
You may give us option to build new layout with less tables, but don't disable the schema already built.
Please please roll back!
This new feature is absolutely useless and disappointing - I didn't notice any improvement in the performance. Moreover, it shouldn't be turned on by default - basing on the experience of other commenters I believe there could be serious issues with the data model and existed relationships because of this "improvement".
I just want to express my disappointment here as well. Disabling the all-table view and suggesting "drag and drop everything and use reset-layout" is totally unaccaptable. The reset feature is not even close to how I like to look at my model.
This must be the worst idea you guys ever had. I need to see my 50+ tables because sometimes the issuses doesn 't shows until y start working. Now I lost visibility of my hole model because of this. I need to see my 50+ Tables immediatly or i will have to change to the competition.
What a horrible update. My overview over all tables is gone. I have to go back to an older backup with a whole day of development gone.... causing serious headache. Isn't there any solution to get back my old all-tables view without losing a day's work?
@Ole111 - This is by design. The All tables layout is specifically disabled in this case where performance cannot be guaranteed. There is no way to recover this state without changing the environment variable and then opening up a PBIX previously saved with the information.
@Ole111 and @johandure - Setting environment variables is a standard windows procedure. Search from the start menu for "Set environment variable" and you will see a window pop up that says "System Properties", in here you can click the button "Environment Variables", then "New", then enter the name PBI_diagramTableThreshold, and then the value (100 for example). Press okay until the dialogs are gone, and then start a new instance of Power BI Desktop. The limit should no longer apply.
@Mohamed_Hashim - Again, this is likely not related to upgrading the model view. Relationships should not be deleted. We recommend starting a support case via your usual mechanism as this is likely something wrong with either your model or a new bug in desktop.
This is a must watch for a message from Power BI!
Click here to read more about the December 2020 Updates!
Click here to read the latest blog and learn more about contributing to the Power BI blog!
Mark your calendars and join us for our next Power BI Dev Camp!.