I have run into an issue with Report URLs that is similar to some reported here but not the same as any I have found.
I have an enterprise arrangement, where I want Dev and Prod PBI/O365 groups for Dev/Test and Deployment of Datasets, Reports and Dashboards, and then I want to use other PBI/O365 groups for different sets of end users so they are all using the one set of data, reports etc, but appropriately filtered. I have Row Level Security on in the Dataset.
I also wanted to use the new Sharepoint Online web part to display reports in our Intranet.
I publish the PBIX to a the DEV group, and then once tested, republish the PBIX to a Prod Group. Dashboards are created in the Prod Group. I then use a Content Pack to distribute certain Dashboards, the Report, and the Dataset to other End User Group (eg Business Unit Groups).
I then user the URL of the report in each BU Group in a BU SPOL Site to provide improved visibility of the report in place. This requires the URL of the Report deployed by the Content Pack.
However, if the content pack is then updated and republished (to deploy any report chart changes or dashboard changes etc) the URL of the Content Pack deployed version of the report changes. The URL of the PROD version reports is consistent (unless I delete the dataset before republishing).
It would be great if the updated content pack reports would retain the same URL so they could be referenced in the SPOL web parts.
I am currently looking at sharing instead of content packs as an option but that isnt working yet because you can.t share to a PBI (O365) Group. If anyone has any ideas on how to solve this, or other approaches to Enterprise deployments it would be great to hear them.
Originally I ony had DEV and then the End User groups, but this makes it hard to test model changes in the Service. It did allow content pack deployment to other groups, but the URL change problem still exists.
The current approach means I have to re-create dashboards in the Prod Group to then deploy them, and I have to use content packs to deploy because I cant Share to other Groups. I suppose I could share to individuals rather than groups but that seems to be a strange approach in a corporate/enterprise setup.
Any advice appreciated.
