Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.
We have a master dataset that is maintained by one team while we allow report developers to build reports using live connection to this dataset. We have 30 plus report created in this way and in production.
The report developers would create DAX measures that are specific to the report requirement that they are working on. But, at times, we feel that the measure should be moved to the master dataset so that every report builder can then use this DAX measure.
Is there a easy way to do this. If we create a measure with the exact name in the master dataset, it works fine for all the reports except for the originating pbix file where they see duplicate measures. Then the developer of that report would have to remap all the measures in that report to use the measure from the master dataset and then have to delete the ones that were created specific to that report.
I think this is a much deeper question. Basically what is the desired behavio(u)r in Power BI when changes in Power Query affect existing meta data in the visual part (measures, calculated columns, groups, hierarchies etc). And conversely, how much should a change in the visual part (renaming a table column for example, or changing its data type) travel back into the Power Query side?
Personally I would vote for a peaceful coexistence between Field and Field(1) rather than the brute force overwrite we see today. But others may have different opinions on that.
@lbendlin - Thanks for the reply. In our case, the situation is not with changes to Power Query. Our issue is on how to move a DAX measure from a live connection PBIX (where the PBIX connects to a master dataset on the Power BI service). Now, a report developer has added a DAX measure to this PBIX file and end users have started using this report and are happy with the same. Now, we wish to promote this measure up to the master dataset so that other report developers can make use of this measure in their live connection PBIX files. When we tried to do this, we get an issue with the originating PBIX file (on the service). This PBIX file records duplicate measures.
Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City
Check out the April 2024 Power BI update to learn about new features.
User | Count |
---|---|
14 | |
2 | |
2 | |
1 | |
1 |