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 traceablity for shared datasets.
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.

Update Dataset without affecting existing reports:

When creating a new report, to utilize existing data set, select 'Power BI datasets' in 'Get Data':

Any changes and additions to existing datasets propagated correctly to reports built on that dataset.

Any removals of data will negatively affect any report built on that dataset.

Naming Convention:

Publishing reports other than using shared datasets from powerBI desktop/service publishes a new dataset based on the report name. So downloading a report from powerbi app, renaming it and publishing it will create a new dataset and report.
Using shared dataset does not. When using shared dataset, model view is not available in shared dataset mode. So no model changes can be made. Although report level measures can still be created, that will be report specific. One cannot used shared dataset with other tables in the report. PowerBI will display a notification message if attempted to do that.

Shared dataset development and report development will then have to be separately handled. Possible a new development strategy needs to be implemented for shared datasets.
One way to do it would be to update the model in the primary/template report and publish it. The primary/template report can then be named in generic way, that describes the dataset. Then delete the report and just keep the dataset, that can then be used as a shared dataset for all the reports. The new reports based on the shared dataset can have appropriate names.

Endorcements ,Dataset certification:

https://docs.microsoft.com/en-us/power-bi/service-datasets-certify

Form Data Cetification Team (determince authorative members)

Tenant Admin gives permision to DCT

DataSet owner Promotes the dataset and requests Certification

DCT certifies and controls use of dataset

Promotion to Beta-Prod:

As of 11/19,

Any changes to the dataset, can't push to PROD or

Workspace for BETA - for customers to review before pushing to PROD or distinct workspace ??? (Discussion needed)

(Needs to be same on Box for version management)

Pipeline demo:

Advantages/Disadvantages of Shared datasets

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

Browser not supported