Power BI is turning 10! Tune in for a special live episode on July 24 with behind-the-scenes stories, product evolution highlights, and a sneak peek at what’s in store for the future.
Save the dateEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
I have created a "master" semantic model for my company's sales data as it is very large, takes a long time to load, and contains many columns that need to be organized. I am now attempting to build multiple reports using this semantic model as the data source for said reports. Each report requires different groupings and calculations that likely will not be needed in any other reports. I am attempting to create new groups/calculated columns within each report, however, I cannot seem to find a way to do this if I use an existing published semantic model. I would really like to avoid having to load and organize the data anew each time, but also do not want unnecessary/unrelated groups and calculations clogging my main semantic model.
I am more familiar with Tableau - where you can pull a Tableau Data Source from the server, then create groups, calculated fields, etc just for a single report/workbook . For example, I have a calculated field for a client's ranking in terms of opportunity that I need for a specific opportunity rankings dashboard, but I don't need that field to appear in any other dashboard. If I create a calculation in my opportunity rankings dashboard, then open another blank report, all of the datasource's calculated fields will be available, but the report-specific ones (such as opp rank) will not be included in the blank report.
Is there any way to achieve this in PowerBI with a semantic model built on redshift data? Thank you.
Solved! Go to Solution.
Hi @prutia ,
In Power BI, when you use a published semantic model as a data source for your reports, the model serves as a single source of truth. This means that while you can use the model across multiple reports, the ability to add report-specific groups or calculated columns directly within the semantic model is limited.
If your semantic model is hosted in Analysis Services or Power BI Premium with XMLA endpoint access, you might consider using calculation groups. Calculation groups allow you to define reusable calculations that can be applied across multiple measures without creating individual calculated columns for each scenario. This feature can help keep your model streamlined while providing flexibility for report-specific calculations. More information on calculation groups can be found here: Create calculation groups in Power BI (preview) - Power BI | Microsoft Learn
Best Regards,
Neeko Tang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hi @prutia ,
In Power BI, when you use a published semantic model as a data source for your reports, the model serves as a single source of truth. This means that while you can use the model across multiple reports, the ability to add report-specific groups or calculated columns directly within the semantic model is limited.
If your semantic model is hosted in Analysis Services or Power BI Premium with XMLA endpoint access, you might consider using calculation groups. Calculation groups allow you to define reusable calculations that can be applied across multiple measures without creating individual calculated columns for each scenario. This feature can help keep your model streamlined while providing flexibility for report-specific calculations. More information on calculation groups can be found here: Create calculation groups in Power BI (preview) - Power BI | Microsoft Learn
Best Regards,
Neeko Tang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Check out the July 2025 Power BI update to learn about new features.
User | Count |
---|---|
71 | |
70 | |
38 | |
28 | |
26 |
User | Count |
---|---|
97 | |
88 | |
60 | |
43 | |
40 |