Thursday, November 11, 2010

The report parameter ‘xxx’ is read-only and cannot be modified.

One of our teams deployed some SRS reports to their Dynamics CRM production environment today. The reports worked fine in both their development and test environments, but definitely did not work in production.

When attempting to run the reports in production, they would get the following [ever so un-helpful] error:

Thankfully, they did already have tracing turned on, so I was able to take a look into the trace files where I found the following exception:

Searching through the blog-o-sphere, I found 2 discussions that suggested re-installing the SRS Connector. Which I did. Which did NOT fix the problem. So, save yourself the time.

Eventually, I found a reference to this article that provides the solution to the problem.

The issue is, that when you import a custom .rdl report into CRM, the Parameters’ visibility setting gets over-ridden and put in a state that causes this problem.

In this team’s case, they had marked all of their Parameters as “internal.” To fix this, they must all be marked as ‘hidden’, but this MUST be done within the SRS report management console and not Visual Studio.

Moral of the story: If you have a report with one or more “internal” Parameters, And you get the exception above, you may have to mark them as “hidden” in the SRS Report Management console for them to work correctly.

About Me

I am the Microsoft Dynamics CRM Sales and Solutions Manager and Evangelist for both Commercial and US Public Sector markets at HCL Americas responsible for supporting sales, business development and marketing for Dynamics CRM in both the Commercial and US Public Sector markets.
This blog covers a very broad spectrum from business conversations to technical conversations to tips and trick on sales and business development.
To help keep my lawyer friends employed... 1) Please note that these are my personal thoughts and ponderings and that they do not represent my employer in any way. 2) Many of these postings discuss unsupported modifications to the products they discuss. If you decide to apply any of these changes to your implementations then neither myself, my employer, nor Microsoft can be held responsible for any issues that it may cause.