Don't miss your chance to take the Fabric Data Engineer (DP-700) exam on us!
Learn moreWe'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
Dear All,
Can Anyone explain how multi tenancy can be enabled in the following Scenario.
I have 10 clients with sales transaction in a single table and a single dashboard, each client will have unique id to identify them.
My requirement is: client 1 should be able to access his own data ( other client (2,3...n) data shouldn't be visible /accessible to client1). Will the data be stored in Cubes? How it works?
1) How would the refresh and extract will happen?
2) how abt the performance?
3) how it can be implemented ?
Thank you
Solved! Go to Solution.
@Beniya_Samson Well, the easiest path to take would be to leverage Row Level Security (RLS). So each customer would be their own role and RLS rules would determine that they only see their own data. Hard to be specific with the information provided. In this scenario, you would have a single data model. And if it is import mode then, yes, it is technically stored as a tabular cube.
@Beniya_Samson Well, the easiest path to take would be to leverage Row Level Security (RLS). So each customer would be their own role and RLS rules would determine that they only see their own data. Hard to be specific with the information provided. In this scenario, you would have a single data model. And if it is import mode then, yes, it is technically stored as a tabular cube.
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 |
|---|---|
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |