Supplies are limited. Contact info@espc.tech right away to save your spot before the conference sells out.
Get your discountScore big with last-minute savings on the final tickets to FabCon Vienna. Secure your discount
Hi All
I have two workspaces; one with data sets in, the other with reports connected to those datasets. The reports and datasets are not housed in the same PBIX files, but each seperate report is connected via the PBI service to the relevant dataset.
I am using a deployment pipeline for the two workspaces to manage changes to reports and data sets respectively. I am only using the test and production elements.
My issue is that each report in the report test workspace is linked to a data set in the data set test workspace. This is because the dataset and report are usually edited together, and the analyst needs to be able to live publish/refresh to see changes feeding through to the report. However, when the report is then published to the production workspace, it is still left connected to the potentially out of date dataset in the dataset test workspace.
The only potential way round this I can see is to have all the test reports linked to the production data sets, so that when publishing the report amendments they are still linked to the correct data source. However, in this case there is seemingly no way to view changes from an updated dataset in a report until actual deployment.
Does anyone have any suggestions? I don't know if this process would be different if I were using a report and datset from a single PBIX file.
Thanks
You can find a detailed answer with a workaround and future updates of the product in this discussion.
Hi @Tim_Giles ,
I didn't find any documents stating whether the report created by dataset across workspace will be affected by scheduled refresh. But what is clear is that report will be refreshed after dataset being refreshed if they are in same workspace.
Best Regards,
Jay