With multiple tables in the model view, the relationship jungle can become a bit overwhelming. Especially, if you need to debug an error in the dataset (say, tables are linked by fields where one table has a certain value that is missing from the other table). For this reason, it would be extremely useful to have a "split view" (upper and lower part) in the model view. The upper part would show the relationships exactly the way they are shown in the model view right now. The lower part would show you the tables you select from the upper part and highlight the columns in tables that are used in the relationship. Filtering options should be made available for all tables separately so that debugging complicated errors becomes easier. If you want to develop this further, you could also add similar functionality to cover "relationships" that are done by using LOOKUPVALUE function.
1 Comment
- fbcideas_migusrNew MemberStatus added:Needs Votes
Recent ideas
Data Pipelines - Run only selected activities
For debugging and testing pipeline activities during development, allow us to select one or multiple activities and run only the selected pipeline activities. For example, I'm working on editing ...frithjof_v22 hours agoCommunity ChampionNew618Views11likes2CommentsSemantic model connection bindings should be in source control (Git)
Semantic model data source connection bindings should be source controlled. A semantic model can contain multiple data source references, each of which can be mapped to a separate Fabric data connec...frithjof_v1 day agoCommunity ChampionNew21Views1like0CommentsBulk changing column names in Visualizations Pane
We often use raw/api column names or measures with a set nomenclature to be consistent and to keep track of them but we do not want to display these names in the visuals. Currently we have to change ...vishal1401971 day agoFrequent VisitorNew6Views0likes0Comments