Support Display Folders for Table Objects
Would love to see Display Folder support added for table objects. This would allow developers to logically group tables by entity\purpose\category\etc so they appear together in the object pane without resorting to forced, unnatural naming conventions or unnecessary normalization.
Please note I am *not* talking about perspectives (which work fine for building targeted subsets of a model to support different groups of users or breaking up large, complex models into more manageable views.) Rather, display folders add a simple and visual way for the modeler to convey additional context to users about the data model and give them a much more streamlined browsing experience which would provide benefit to even the simplest models.
For example
Dates:
Due Date Dim
Order Date Dim
Ship Date Dim
Employee:
Sales Employee
Shipping Employee
Parameter Tables:
Rolling N Days
Product Weights
Sales Scaling
Jonathan Kazyak
shared this idea
Agreed. There are dependencies on client tools, but we want to do this.
2 comments
-
Kazyak, Jonathan
commented
Thanks for the reply.
I understand that it's ultimately up to the client to choose to implement but is that really a reason why can't be added to the spec? Clients are *never* going to implement (or even think about implementing) a functionality that doesn't exist. Since display folders are optional and aren't engine related, adding it to a new compatibility level shouldn't break existing functionality. Clients target that version or above can choose to implement (or not).
I'm a huge fan SSAS Tabular but it seems that for a tool billed as a semantic model its biggest limitation is having the logical model displayed to end users dictated by the underlying physical structure. -
Thank you for the feedback. We've received it from a few customers and we'd love to get to it!