Forum Discussion
multiple or single semantic model
Hi powerbiexpert22,
Use Single Model + RLS when departments share the same fact tables and need a unified source of truth. RLS handles row-level restriction per user/department. Simpler to maintain, consistent KPIs.
Use Multiple Model when structures diverge, split when :
- Different grain (HR = employee level, Finance = GL line level)
- Sensitive data isolation required (payroll ≠ visible even as metadata to Finance)
- Different refresh cadences or development team ownership
- Model becomes a bloat of irrelevant measures per audience
The real-world best practice to avoid duplication is using Hybrid Model which means having one certified core model for shared dimensions (Date, CostCenter, OrgUnit) → department models connect via composite/live connection and add their own facts and measures. No dimension duplication, clean ownership per team.
How to choose the right pattern ? start with one model + RLS, split only when you hit a structural or compliance constraint.
Hi powerbiexpert22,
If the requirements for all departments are the same, you can proceed with the RLS. Less effort in maintenance.
However, if each department has its own requirements, then you need to proceed with multiple models. It requires more effort in maintenance but you'll be sure that there will be no any data mix up.
Hope this helps.