Trying to port an RDL report to VS2005. Getting the following error on all
CRM_
parameters in the report.
The report parameter 'my-parameter-here' is read-only and cannot be modified.
I did not have this problem in VS2003 Reporting. Any ideas or answers from
anyone?
CRM 4.0
VS2005 all SP's
SQL2005
Typically the only thing that I change is the data source from
localhost to the SQL server name if I am running on my local computer.
<ConnectString>data source=localhost;
from the XML source of the report.
<?xml version="1.0" encoding="utf-8"?>
<Report
xmlns="http://schemas.microsoft.com/sqlserver/reporting/2005/01/reportdefinition"
xmlns:rd="http://schemas.microsoft.com/SQLServer/reporting/reportdesigner">
<DataSources>
<DataSource Name="CRM">
<rd:DataSourceID>05ddfd4d-9c76-4724-9731-e23b1c5b9e0f</rd:DataSourceID>
<ConnectionProperties>
<DataProvider>SQL</DataProvider>
<ConnectString>data source=localhost;initial
catalog=MicrosoftCRM_MSCRM</ConnectString>
<IntegratedSecurity>true</IntegratedSecurity>
</ConnectionProperties>
</DataSource>
</DataSources>
After opening your report in VS2005 click on the Layout tab.
Then off the main menu choose Report -> Report Parameters
Click on your parameter in the parameter list.
There are a number of checkboxes that you can select.
Including Internal and whether your value come from a query or not.
Your answer should be somewhere in there.
Are you dealing with a Sub-Report? That is new for CRM 4.0 and they
rely on a parent report that pulls the data and transfers information
using internal parameters.
--
Mark Kovalcson
MS CRM Solutions Architect & Developer
http://crmscape.blogspot.com
Thanks for your response. Porting may be the wrong term. It is a report
that runs fine built in VS2003. It will not compile correctly once opened
and convered in 2005.
The report does have a subreport associated with it. I cannot successfully
run the report in the dev environment, I get these errors on every CRM_
parameter in the report. It doesn't make sense to me as a parameter is a
parameter. It could have something to do with the subreport.