Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change report data source on deploy #179

Open
fredrikheden opened this issue Aug 16, 2022 · 5 comments
Open

Change report data source on deploy #179

fredrikheden opened this issue Aug 16, 2022 · 5 comments

Comments

@fredrikheden
Copy link

Hi!

I have the need to deploy a report to different workspaces and reconfigure the data source for it when deploying. Currently, I am using a “workaround” where I am replacing the Connections.json file before each report deployment.

Maybe this functionality already exists, although I could not find it in the documentation/samples? If not, any plans of adding it?

/ Fredrik

@matherring
Copy link

Came here to ask the same.

@picious
Copy link

picious commented Aug 19, 2022

Hi, I have 3 env. (DEV,UAT and PROD) , and created 2 report files and 2 datasets , one Dataset in Dev and one in PROD , so reports in DEV and UAT are having as source the dataset in DEV and report in prod the dataset in prod.. we are making chaning on the report in DEV env then moving to UAT if approved then we make changes on the Prod report (As mentioned above).
Switching report connections as part of deployments is requested !!!!!

@ScottShelby
Copy link

Same.

@mthierba mthierba pinned this issue Aug 25, 2022
@ingthu
Copy link

ingthu commented Dec 4, 2022

Hi Mathias!

Thank you for a very goog tool!

We are using pbi-tools for deployment of datasets together with azure pipelines. This is working perfect!
But we also would like to use report deployment, but to use this feature we need to be able to change the data source connection on deploy cause the dataset can be stored in another workspace. Do you have any plans to add this feature?

@mthierba
Copy link
Contributor

mthierba commented Dec 5, 2022

@ingthu It's on the roadmap, but due to other commitments not before January. The backend code is already in place as it was developed for #141, but this needs some frontend work. Feel free to send a PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants