Need the ability to bind report to different data set explicitly
Sometimes, there are some modifications to the underlying data set and to update it, currently you need to delete the dataset which will delete all the reports. This requires recreating the reports every time when you want to modify the dataset.
Should be able to bind report to different data set explicitly as long as they have same table/fields.
Or maybe if we can export report's definition and easily recreate report from definition will also be good.
Great suggestion! We can add more features in general to the management of datasets and reports – repointing a report at a different dataset is a great example. Please keep adding votes if you think this would be useful!
Another use case - we want to create a report template and have non expert users use that template with csv files they create
I built the model used a test/dev database connection. After publishing to PowerBI.com, I'd like to change the database connection to a production database.
Yehonatan Ginzberg commented
Today I cannot tell what is the dataset of the report (besides naming them the same).
Adding Reports' metadata/information with this information will solve it for me. Other solutions are welcomed :) (e.g. add data source name above the table name in the fields pane)
chung wong commented
This is definitely necessary. I cannot update my excel if there is any structural changes because all my reports will no longer work.
Daragh Fitzpatrick commented
The ability to run an impact/dependency check (i.e., what would a metadata or design refresh 'break') would mitigate this. It's not just the data-set, but anywhere in the lineage. The workaround is to redirect the query to a wrapper query that meets the original contract.
Please see my request around meta-data management.