...
Kateryna Monastyrska (Deactivated)
...
Traceability back to source:
When looking at a report created from a dataset, there is not a method to identify the source of field data from the browser. No impact on data traceblity .
Step 1: Identify the dataset the report uses.
Step 2: Download a local copy of the dataset from app.powerbi.com
Step 3: Edit the query that generates the table in question in the downloaded local copy.
Step 4: Read through the rename step in the query on the right hand side by viewing the native query.
...
Any removals of data will negatively affect any report built on that dataset.
Naming Convention:
Publishing new reports from powerBI desktop create a dataset based on the report name. Using shared dataset does not, but model view is not available in shared dataset mode. Shared dataset development and report development will then have to be separately handled. One way to do it would be to update the model in the primary/template report and publish it. Then create/update new/existing report created using shared dataset.
Endorcements ,Dataset certification:
...
Above graphic from: https://www.blue-granite.com/blog/power-bi-shared-datasets-for-self-service-bi
Also
- Shared datasets across workspaces are only supported with the new workspace experience
- While developing using shared datasets one cannot see or change the model.
- Linked shared dataset used in a different workspace cannot be removed, if the only report using it is deleted
- If shared dataset to be used for internal report development (non self bi users), that strategy will have to be reconsidered. (Publishing reports with shared datasets from powerBI desktop seem to create another dataset based on the report name. Shared dataset development and report development will then have to be separately handled. One way to do it would be to update the model in the primary report and publish it. Then create/update new/existing report created using shared dataset.)