We need true role playing capabilities for dimensions in Fabric. Currently, you can include a table only a single time in a semantic model that uses DirectLake. This makes it impossible to use a dimension as a role playing dimension - for example, our date table as admit date, discharge date, surgery date, etc. Also the same for providers - there can be an admitting provider, discharge provider, attending provider, surgeon, primary care physician, etc.
We need the ability to:
- Use a table multiple time in a semantic model built in the service
- Be able to rename the table, for example rename a generic "date" table to admit date, discharge date, etc.
- Still have everything work properly with DirectLake
The only workaround currently is to create multiple copies of the table. This not only wastes space, but also means separate ETLs have to be updated if there's any change to the base table.
Thanks,
Scott
Chris_Novak1
on:
Email notification on Interactive Delay
frithjof_v
on:
Show soft deleted storage size in Capacity Metrics...
on:
Footnotes for visuals