Improve SSRS report publishing
Publishing SSRS reports sometimes does not reset the data source to the default MSCRM_DataSource in the CustomReports folder; it must be manually changed by connecting to Report Manager and resetting it there. Also, new reports in CRM do not get a "Display In:" setting of "Reports area", requiring one to find the report in the "All reports" view and set this before it will appear in the "My Reports" view; it would be nice to automatically apply these settings by default.
Kevin
shared this idea
Hi Kevin, the ability to modify the majority of the different report properties (including the ability to set the ‘Display In’) is available in v4 that was released today.
-
Hi Kevin,
Thanks for the additional info. My guess is that it's something that has to do with your environment. Behind the scenes, CRM Solution Manager is doing the same thing as if you had manually uploaded the report using the CRM GUI. It doesn't interact directly with SSRS. CRM takes care of this behind the scenes and would be the mechanism that would probably update any connection info using the CRM SSRS connector that gets installed as part of the CRM setup.
-
Kevin
commented
I've run into the data source (DS) issue several times, but it's odd, hard to reproduce. The last time I saw it was after refreshing a Staging CRM environment from the Production environment
The only way I've found to recreate it is to access an existing report in Report Manager, change its DS from the default shared DS back to a Custom DS with type = Microsoft SQL Server and an appropriate connection string (Data Source=<SQLServer>;Initial Catalog=<ORG>_MSCRM), then open it in Visual Studio and select "Add SSRS Report file to CRM". In Report Manager, the report still has the DS set to the Microsoft SQL Server type with the basic connection string. If you then download the report with CRM Solution Manager, test, build, etc. and publish it back to CRM, the DS never gets reset to the Microsoft Dynamics CRM SQL type. Maybe it's just an issue with our custom CRM environments; if it happens again, I'll try to get more info on how/why...