Home/ Questions/Q 8699451
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-13T01:57:00+00:00

I have a Reporting Services 2005 report that had an error: Parameter UserID is

  • 0

I have a Reporting Services 2005 report that had an error: “Parameter UserID is read-only”. After doing some research, I found a solution that worked. I opened the report from the Report Manager web interface and changed this:

before

..to this:

after

After this change, the report works! Great!

So, I figure I will download the modified RDL so I can see the change and get the corrected RDL into my source code repository. So, I download the RDL:

Downloading the RDL

But my diff tools tell me that the “before” version of the RDL is identical to the “after” version of the RDL. Convinced that my diff tool was mistaken, I tried another. Sure enough, there is no difference in the RDL.

What am I missing? Is the change reflected somewhere other than the RDL, or is Reporting Services not coughing up the correct version of the RDL? In either case, how can I get the correct version of the RDL?

Thank you.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    TL/DR Version: Reporting Services is not giving you the correct RDL.

    Your question prompted me to further investigate a suspicion I already had on SSRS for quite some time: report parameters can behave in unexpected ways for report developers when deploying (or downloading) report definitions. One related scenario I had noted before:

    1. Create a report with parameters.
    2. Deploy the report for the first time.
    3. Update the report parameters in some way.
    4. Deploy the same report once more.
    5. Result: parameter settings are not succesfully updated on the server.
    6. Delete the report from the report manager.
    7. Deploy the report once more (effectively the same as step 2).
    8. Result: Report parameters are updated correctly.

    In short, if you want to update parameter settings for deployed reports you’ll first need to delete it and then deploy it, or update the settings directly via the report manager.

    Back to your question(s). You’re not missing anything, this just seems the way SSRS is behaving (intended or not). The RDL schema has this (abbreviated) piece:

    <xsd:complexType name="ReportParameterType">
    <xsd:choice minOccurs="1" maxOccurs="unbounded">
        <xsd:element name="DataType">
            <!-- abbreviated -->
        </xsd:element>
        <xsd:element name="Nullable" type="xsd:boolean" minOccurs="0"/>
        <xsd:element name="DefaultValue" type="DefaultValueType" minOccurs="0"/>
        <xsd:element name="AllowBlank" type="xsd:boolean" minOccurs="0"/>
        <xsd:element name="Prompt" type="xsd:string" minOccurs="0"/>
        <xsd:element name="ValidValues" type="ValidValuesType" minOccurs="0"/>
        <xsd:element name="Hidden" type="xsd:boolean" minOccurs="0"/>
        <xsd:element name="MultiValue" type="xsd:boolean" minOccurs="0"/>
        <xsd:element name="UsedInQuery" minOccurs="0">
    </xsd:choice>
    <xsd:attribute name="Name" type="xsd:normalizedString" use="required"/>
</xsd:complexType>

    So, there should be a “Hidden” element for your ReportParameter.

    I just verified your findings (in SSRS 2008), and think I may have the answer to your second question: SSRS is indeed not coughing up the correct version of the RDL. It’s missing various bits about the parameters, including the element on being hidden or not.

    Funny thing is: if you change the report in BIDS and set the parameter to hidden, the RDL will be changed and have the <Hidden>true</Hidden> element.

    • 0