Showing posts with label rdl. Show all posts
Showing posts with label rdl. Show all posts

Tuesday, March 20, 2012

parent and child reports

Please help me, is there a way to get the field.value from another report?

example:
report1.rdl:
id: 01 < field!id.value
name | age | sex
nemo 11 m
id: 02
...
I want the field!id.value to be used by report2.rdl, so i can make a parent -child way:

id: 01 < report1.rdl
name | age | sex
nemo 11 m

friend | school | teacher <--report2.rdl,a subreport with id:01 from report1.rdl
sha ppch yanimoto

As you have already indicated, you can use a subreport and just pass the current id-value as parameter to the subreport. In the subreport make sure the report parameter value is used in the query to just retrieve the data with the according parameter value.

-- Robert

Parametrization of xsd:boolean RDL element

Hi,

I'm trying to parametrize <CanGrow> element of the TextBox. It has xsd:boolean type, so when i assign this element with a simple expression like this:

<CanGrow>=Parameters!CanGrow.Value<CanGrow>

I get the following error:

Deserialization failed: The 'http://schemas.microsoft.com/sqlserver/reporting/2005/01/reportdefinition:CanGrow' element has an invalid value according to its data type. Line 782, position 59.

because resulted XML doesn't satisfy RDL schema.

The same expression in <Hidden> element does'n involve the error, because <Hidden> has xsd:string type.

Is there any way to have xsd:boolean report element parametrized, but not hardcoded?

I've made no progress on this issue.

Could anybody explain me how to parametrize xs:boolean report elements?

Thanks.

|||Any ideas on this issue?|||

Per the RDL specification (http://www.microsoft.com/sql/technologies/reporting/rdlspec.mspx), the CanGrow element is a constant boolean value. Expressions are not supported for CanGrow.

-- Robert

|||Thaks, Robert!

But in this case why not to make all xsd:boolean RDL elements of type

xsd:string? By the way, some RDL element with true/false values already

are of xsd:string type (ex. <VisibilityType><Hidden>).

Wednesday, March 7, 2012

Parameters defined in .rdl and how they are applied in Report Manager

One of my reports is defined as follows in .rdl:

<ReportParameter Name="ExplicitProject">
<DataType>String</DataType>
<DefaultValue>
<Values>
<Value>Agile_1029c</Value>
</Values>
</DefaultValue>
<AllowBlank>true</AllowBlank>
<Prompt>ExplicitProject</Prompt>
</ReportParameter>

In Report Manager, I have overriden this value by specifying that the default value be an empty string. The report uses the value I specified in Report Manager.

How does this work? Where does Report Server store the overriden definition? There seem to be two places where the rendering is getting its specification. Is there a hierarchy i.e. first check .rdl, then check (wherever the overrides are stored?)

Kind Regards
Jean-Pierre

The overridden parameters are stored in the report catalog. If you override the report parameters in the Report Manager and subsequently deploy the report definition with new default values, you will find that the parameter default values don't change. This is done to favor the report administrators. You can only change default values of a deployed report programatically. The other option is to delete the report and re-deploy.|||

Thank you Teo. THis has been of great help.

Parameters Caching?

Hello,
I've created a report (with default parameters) and uploaded it to Report
Manager.
When I later change the default parameters in the RDL and "Update" the
report definition, the default parameters do not update in Report Manager.
When I remove the report definition and re-upload it, the report parameters
are once again updated.
My theory is that when I upload a report, the parameters are stored in a
table in the ReportServer database, and pulled from there no matter what is
contained in the report definition. If this is the case, is there a way to
"Refresh" the default parameters?
Any assistance would be greatly appreciated.
Best Regards,
BenAfter you deploy the report to the server with the change. Close IE and
re-open it. You should see the new report then.
Bruce L-C
"Benjamin Pierce" <bpierce@.opentext.com> wrote in message
news:OWB78$vfEHA.644@.tk2msftngp13.phx.gbl...
> Hello,
> I've created a report (with default parameters) and uploaded it to Report
> Manager.
> When I later change the default parameters in the RDL and "Update" the
> report definition, the default parameters do not update in Report Manager.
> When I remove the report definition and re-upload it, the report
parameters
> are once again updated.
> My theory is that when I upload a report, the parameters are stored in a
> table in the ReportServer database, and pulled from there no matter what
is
> contained in the report definition. If this is the case, is there a way
to
> "Refresh" the default parameters?
> Any assistance would be greatly appreciated.
>
> Best Regards,
> Ben
>|||Hello,
I've attempted to refresh the report (and have cleared my cache), but to no
avail.
If I issue this query, I can see that the old parameters are still sitting
in the catalog table.
SELECT Parameter FROM Catalog
It looks like updating a report definition on your report manager doesn't
actually change the default parameters in the Catalog table, even if they
have changed in the updated RDL.
Does this seem like a bug to anybody? I'm more than happy to provide an
easy to setup example if requested.
Thanks again,
Benjamin Pierce
Open Text Corporation
"Bruce Loehle-Conger" <bruce_lcNOSPAM@.hotmail.com> wrote in message
news:O%23BKBJwfEHA.1428@.TK2MSFTNGP10.phx.gbl...
> After you deploy the report to the server with the change. Close IE and
> re-open it. You should see the new report then.
> Bruce L-C
> "Benjamin Pierce" <bpierce@.opentext.com> wrote in message
> news:OWB78$vfEHA.644@.tk2msftngp13.phx.gbl...
> > Hello,
> >
> > I've created a report (with default parameters) and uploaded it to
Report
> > Manager.
> >
> > When I later change the default parameters in the RDL and "Update" the
> > report definition, the default parameters do not update in Report
Manager.
> > When I remove the report definition and re-upload it, the report
> parameters
> > are once again updated.
> >
> > My theory is that when I upload a report, the parameters are stored in a
> > table in the ReportServer database, and pulled from there no matter what
> is
> > contained in the report definition. If this is the case, is there a way
> to
> > "Refresh" the default parameters?
> >
> > Any assistance would be greatly appreciated.
> >
> >
> > Best Regards,
> >
> > Ben
> >
> >
>|||It is actually our design, although an arguably strange one. Report
parameters can be modified after the report has been published and we
decided to favor the admin over the developer and not overwrite them by
default when the report definition is changed. If you want to do so, you
would need to call SetReportParameters after SetReportDefinition.
--
Tudor Trufinescu
Dev Lead
Sql Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Benjamin Pierce" <bpierce@.opentext.com> wrote in message
news:uzXTMVwfEHA.3928@.TK2MSFTNGP11.phx.gbl...
> Hello,
> I've attempted to refresh the report (and have cleared my cache), but to
no
> avail.
> If I issue this query, I can see that the old parameters are still sitting
> in the catalog table.
> SELECT Parameter FROM Catalog
> It looks like updating a report definition on your report manager doesn't
> actually change the default parameters in the Catalog table, even if they
> have changed in the updated RDL.
> Does this seem like a bug to anybody? I'm more than happy to provide an
> easy to setup example if requested.
>
> Thanks again,
> Benjamin Pierce
> Open Text Corporation
>
> "Bruce Loehle-Conger" <bruce_lcNOSPAM@.hotmail.com> wrote in message
> news:O%23BKBJwfEHA.1428@.TK2MSFTNGP10.phx.gbl...
> > After you deploy the report to the server with the change. Close IE and
> > re-open it. You should see the new report then.
> >
> > Bruce L-C
> >
> > "Benjamin Pierce" <bpierce@.opentext.com> wrote in message
> > news:OWB78$vfEHA.644@.tk2msftngp13.phx.gbl...
> > > Hello,
> > >
> > > I've created a report (with default parameters) and uploaded it to
> Report
> > > Manager.
> > >
> > > When I later change the default parameters in the RDL and "Update" the
> > > report definition, the default parameters do not update in Report
> Manager.
> > > When I remove the report definition and re-upload it, the report
> > parameters
> > > are once again updated.
> > >
> > > My theory is that when I upload a report, the parameters are stored in
a
> > > table in the ReportServer database, and pulled from there no matter
what
> > is
> > > contained in the report definition. If this is the case, is there a
way
> > to
> > > "Refresh" the default parameters?
> > >
> > > Any assistance would be greatly appreciated.
> > >
> > >
> > > Best Regards,
> > >
> > > Ben
> > >
> > >
> >
> >
>|||Thank you sir!
Your workaround is quite acceptable.
Regards,
Benjamin Pierce
"Tudor Trufinescu (MSFT)" <tudortr@.ms.com> wrote in message
news:ulCejkwfEHA.3024@.TK2MSFTNGP10.phx.gbl...
> It is actually our design, although an arguably strange one. Report
> parameters can be modified after the report has been published and we
> decided to favor the admin over the developer and not overwrite them by
> default when the report definition is changed. If you want to do so, you
> would need to call SetReportParameters after SetReportDefinition.
> --
> Tudor Trufinescu
> Dev Lead
> Sql Server Reporting Services
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
> "Benjamin Pierce" <bpierce@.opentext.com> wrote in message
> news:uzXTMVwfEHA.3928@.TK2MSFTNGP11.phx.gbl...
> > Hello,
> >
> > I've attempted to refresh the report (and have cleared my cache), but to
> no
> > avail.
> >
> > If I issue this query, I can see that the old parameters are still
sitting
> > in the catalog table.
> >
> > SELECT Parameter FROM Catalog
> >
> > It looks like updating a report definition on your report manager
doesn't
> > actually change the default parameters in the Catalog table, even if
they
> > have changed in the updated RDL.
> >
> > Does this seem like a bug to anybody? I'm more than happy to provide an
> > easy to setup example if requested.
> >
> >
> > Thanks again,
> >
> > Benjamin Pierce
> > Open Text Corporation
> >
> >
> > "Bruce Loehle-Conger" <bruce_lcNOSPAM@.hotmail.com> wrote in message
> > news:O%23BKBJwfEHA.1428@.TK2MSFTNGP10.phx.gbl...
> > > After you deploy the report to the server with the change. Close IE
and
> > > re-open it. You should see the new report then.
> > >
> > > Bruce L-C
> > >
> > > "Benjamin Pierce" <bpierce@.opentext.com> wrote in message
> > > news:OWB78$vfEHA.644@.tk2msftngp13.phx.gbl...
> > > > Hello,
> > > >
> > > > I've created a report (with default parameters) and uploaded it to
> > Report
> > > > Manager.
> > > >
> > > > When I later change the default parameters in the RDL and "Update"
the
> > > > report definition, the default parameters do not update in Report
> > Manager.
> > > > When I remove the report definition and re-upload it, the report
> > > parameters
> > > > are once again updated.
> > > >
> > > > My theory is that when I upload a report, the parameters are stored
in
> a
> > > > table in the ReportServer database, and pulled from there no matter
> what
> > > is
> > > > contained in the report definition. If this is the case, is there a
> way
> > > to
> > > > "Refresh" the default parameters?
> > > >
> > > > Any assistance would be greatly appreciated.
> > > >
> > > >
> > > > Best Regards,
> > > >
> > > > Ben
> > > >
> > > >
> > >
> > >
> >
> >
>