You’re offline. This is a read only version of the page.
80
We are planning to introduce FetchXML based SSRS Reports within the system for Reporting and hence wanted to arrive at a process of migration of the developed Reports from the development environment to the Test environments which would fit into our existing process of automated deployments.
In this context could someone suggest the best practice for using dynamic connection strings within SSRS Report so that the parameters are populated automatically for different servers and Organisations. Also how do we pass the credentials in this case, since the reports user would be named differently on the servers.
Thanks & Regards
*This post is locked for comments
Well I had a look at the Report Server Manager and it appears the connection string is unchanged between environments when solution is imported however the default shared FetchXML datasource for that environment is used instead.
Thanks, It does indeed appear to work with the Report Server magic where it ignores the connection string set within.
Do you happen to also know if we can test these Reports in any automated way or is only manual testing the way forward.
Regards
Yes, it will be replaced.. just give it a try.
As for the mechanics.. Apparently CRM knows the server/organization when you are deploying the report to CRM(since you are deploying into a particular organization on a particular server), so it can easily replace those parameters in the connection string.
Hi Alex,
Sorry, I dont quite follow. If I place connection as "DEV_ServerURL;Dev_OrganizationName" in the Report .rdl file and test in DEV to be part of solution and then import the same solution into Test ,would the connection string be replaced as "TEST_ServerURL;TEST_OrganizationName" automatically by CRM. Also how would this scenario handle two organisations on same Server ?
Hi VBDynamics,
from the CRM standpoint, you can simply include those reports into a solution file, export them from dev, and import them to the target environment. CRM will update all connection strings automatically at the time of import.
You just need to make sure your connection string follows this format:
technet.microsoft.com/.../dn531151.aspx
"ServerURL;OrganizationName;HomeRealmURL
In this connection string, only ServerURL is mandatory. If OrganizationName isn't specified, the first organization that the user running this query belongs to is used. HomeRealmURL is the Home Realm URL of the Identity Provider used by your organization and is needed when your organization uses Federation for identity management. Contact your network administrator to determine the Home Realm URL."
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,240
Super User 2024 Season 2
#2
Martin Dráb
230,149
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (