How to avoid embedding a connection string in a SQL Server Dynamics CRM 2011 report?

I used BIDS (VS2008) to develop a SQL query report for an instance of Dynamics CRM 2011. This is done OK in the VS preview, but I am puzzled by how to deploy it because the database connection string is hard-coded in the RDL file. Of course, this should not be present in RDL, because it will make it impossible to promote the report through DEV, UAT and LIVE? I suspect that I missed something quite simple, but if someone could advise me, I would appreciate it.

+4
source share
2 answers

My assumption is that when you pull it through the report manager, there is a mechanism that will change the connection string in the report to the target system. I did not dig deep to try to figure this out, but I had no problem deploying rdl files before. It just works automatically.

+2
source

When you deploy the report to CRM, it will use any connection strings and make sure that they point to the correct CRM database. This can cause problems if you use a different external database, but there is work around. But for a simple report that uses only CRM data, you don’t need to do anything

+2
source

Source: https://habr.com/ru/post/1480460/


All Articles