Need Help Creating Generic Measures Based on Dynamic Table Selection by Organization

Hi raaan12,

Thanks for reaching out to the Microsoft fabric community forum.

It looks like you are trying to developing a Power BI dashboard that will be embedded in a web application. The application will support multiple organizations, and each organization has its own dataset stored in a separate table following a consistent naming convention. Power BI's current architecture doesn’t support dynamic table binding based on a runtime parameter. So unless the collections can be unified efficiently at the source or via an API layer, the options are either maintaining separate models per org or building a scalable back-end abstraction to serve the right data from a single logical table.This kind of setup, where each organization has its own table with the same schema, is a common pattern but can introduce complexity in Power BI, especially when trying to build a single, maintainable semantic model that supports dynamic behavior based on user context.

Given your setup in MongoDB with one collection per organization (e.g., X_booking, Y_booking, etc.), and the fact that each has the same schema but different data, I can see why combining everything into a single table isn’t working for you especially with the performance and maintenance challenges you mentioned.

You're right that Power BI doesn’t currently support dynamic switching between tables based on a runtime parameter or user context. DAX can’t dynamically reference a table name, it has to be hardcoded. That’s the main blocker in trying to create a “generic” semantic model using separate tables.

Since you're using MongoDB, one option might be to introduce a lightweight middleware layer (e.g., an API or a database view) that consolidates data from the relevant collection at query time based on the organization code. This would allow Power BI to always connect to a single logical table, and that table would return only the data for the active organization. If you’re embedding, you can pass the organization code as a parameter to the API. This avoids bringing all data into Power BI and helps with performance and scalability.

You can also use Power BI parameters, and while they don’t work dynamically in DAX, you can use them to control which table or query gets loaded but this only works at refresh time, not at runtime in the embedded view. It’s more useful in a desktop/development scenario or when triggering dataset refreshes via the REST API.

I would also take a moment to thank Deku, for actively participating in the community forum and for the solutions you’ve been sharing in the community forum. Your contributions make a real difference.

If I misunderstand your needs or you still have problems on it, please feel free to let us know.  

Best Regards,
Hammad.
Community Support Team

If this post helps then please mark it as a solution, so that other members find it more quickly.

Thank you.