I have a report where I use Globals!ReportName in the header of the report
for the report title. In Development and on SSRS stand alone the value for
Globals!ReportName is in mixed case and the file extension is omitted. When
the report is published to a MOSS server integrated with SSRS the value for
Globals!ReportName is all in lower case and the file extension is included.
Is there any reason for this change in behavior and is there a way I can put
back the mixed case and omit the file extension?I just noticed this is also affecting the root level of the Document Map with
one exception. The case is all in lower case but the file extension is
omitted when rendered on MOSS. It works fine on SSRS.
"Ben Holcombe" wrote:
> I have a report where I use Globals!ReportName in the header of the report
> for the report title. In Development and on SSRS stand alone the value for
> Globals!ReportName is in mixed case and the file extension is omitted. When
> the report is published to a MOSS server integrated with SSRS the value for
> Globals!ReportName is all in lower case and the file extension is included.
> Is there any reason for this change in behavior and is there a way I can put
> back the mixed case and omit the file extension?
Sunday, February 26, 2012
Globals!ReportName behaves differently when SSRS integrated with M
Labels:
alone,
behaves,
database,
differently,
globalsreportname,
header,
integrated,
microsoft,
mysql,
oracle,
report,
server,
sql,
ssrs,
value
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment