I’m working on a Proof of Concept (POC) to create a generic semantic data model using Tabular Editor that connects to multiple datasets for Power BI reports. The goal is to have one centralized semantic data model deployed in Tabular Editor while allowing Power BI reports to use their respective datasets.
Key Objectives: A single semantic model is to be maintained and deployed in Tabular Editor. Different Power BI reports are connected to their own datasets. Ensure flexibility in data source connectivity while keeping the semantic model generic and reusable.
Challenges: How to architect the connections between the semantic model and multiple datasets. Maintaining data consistency and ensuring no redundant model deployments. I’d like to know if anyone in the community has achieved a similar setup and can share guidance or best practices for implementing this approach. Specifically:
Can this be achieved with perspectives, calculation groups, or other advanced features of Tabular Editor? Are there any considerations for managing relationships, partitions, or dataset-specific logic in this setup? I appreciate any insights, examples, or references you can share. Thank you!
You should create a single master model, and deploy three copies of it, each connected to a single client’s data.
A common approach is to have a separate workspace for each client.