-
Notifications
You must be signed in to change notification settings - Fork 21
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
Question: Reference Datasource in Reports without overwriting the Datasource #68
Comments
OK, I solved it and just deploy the reports and then use some functions I found via Google in combination with Pipeline Variables to update the datasource reference. function Global:Get-SSRS
} function Global:Get-SSRSReport
} function Global:Get-SSRSSharedDataSource
} function Global:Set-SSRSReportDataSource
}
|
Hi Alex What I have found is that deploying an update to an existing report is fine anyway - it retains whatever datasource linking it already has. So this is only an issue for new reports. That script does the job well for new reports so thanks for that. I think I will look to build it into my pipeline release by putting it into a standard-named file in the project with the relevant values for the relevant commit - we already have to do that for the extension's deployment configuration json file. It would be really great if the extension itself could link up datasources like this though. I have used SSRS at two sites, and both have their datasources defined independently on the server and not in the project. Thanks again for the script. Steve |
Dear author mmajcica,
I have several reports that use the same Shared Datasource and two environments (TEST/PROD).
The Shared Datasource is called ODS1 and uses Windows Credentials with Username/PWD saved in the Datasource.
TEST and PROD environment have the ODS1 in the same location, but use different Connection Strings and Username/PWD.
The idea is that these ODS1 are manually created in TEST/PROD environment and should not be changed or overwritten by the DevOps Pipelines.
Reports should be deployed/overwritten by DevOps pipelines to both environments.
At the moment it seems that this is not possible.
When I just have the reports in the configuration json, they get deployed but the Datasource is not referenced and that needs to be manually done after deployment.
When I have the datasource and the reports in the configuration json, then the datasource gets properly referenced in the reports which is fine if you have just one environment, but at the moment it creates the Datasource on PROD with the Connectionstring/User/PWD of the TEST environment.
Is there an option to NOT overwrite existing Datasources, but overwrite existing reports and still reference the Datasources in the reports after deploying? The Datasources are named identically in both environments and are at the same path, so that should not be an issue.
best regards
Alex
The text was updated successfully, but these errors were encountered: