Device Information Settings - SimplePageHeader

I am trying to use the new SimplePageHeader device information setting
which was introduced in RS SP1 for Excel exporting but have not seen
any impact when using the setting. Following is an example of how I
am using the setting in an URL:
...ReportName&rs:Command=Render&rs:Format=EXCEL&rc:SimplePageHeader=True
My motivation for using this setting was an attempt to stop the export
from merging several of the columns in the report since this results
in the error "This operation requires the merged cells to be
identically sized" when trying to sort on various columns within
Excel. My thought was that by moving the header out of the actual
worksheet (which is my understanding from the documentation of what
the setting is supposed to do), the rendered report may not need to
merge cells to get the output formatted properly. Any suggestions
would be appreciated.I think the device info is SimplePageHeaders.
--
Nico Cristache [MSFT]
Microsoft SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"f_mumble" <fred_mumble@.yahoo.com> wrote in message
news:5e9391dd.0406281737.724e4c66@.posting.google.com...
> I am trying to use the new SimplePageHeader device information setting
> which was introduced in RS SP1 for Excel exporting but have not seen
> any impact when using the setting. Following is an example of how I
> am using the setting in an URL:
> ...ReportName&rs:Command=Render&rs:Format=EXCEL&rc:SimplePageHeader=True
> My motivation for using this setting was an attempt to stop the export
> from merging several of the columns in the report since this results
> in the error "This operation requires the merged cells to be
> identically sized" when trying to sort on various columns within
> Excel. My thought was that by moving the header out of the actual
> worksheet (which is my understanding from the documentation of what
> the setting is supposed to do), the rendered report may not need to
> merge cells to get the output formatted properly. Any suggestions
> would be appreciated.|||Thanks for the follow-up, but adding the 's' didn't make a difference.
Are my expectations of what this device info setting supposed to
accomplish accurate?
As a test I completely removed the header from the report, and as I
suspected the columns are no longer merged in Excel. As a result,
Excel is able to sort any of the columns with no problems.
Unfortunately, having no header on the report is not an option, so any
other suggestions are welcome.
"Nico Cristache [MSFT]" <nipirvan@.microsoft.com> wrote in message news:<uFBPjyXXEHA.796@.TK2MSFTNGP10.phx.gbl>...
> I think the device info is SimplePageHeaders.
> --
> Nico Cristache [MSFT]
> Microsoft SQL Server Reporting Services
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "f_mumble" <fred_mumble@.yahoo.com> wrote in message
> news:5e9391dd.0406281737.724e4c66@.posting.google.com...
> > I am trying to use the new SimplePageHeader device information setting
> > which was introduced in RS SP1 for Excel exporting but have not seen
> > any impact when using the setting. Following is an example of how I
> > am using the setting in an URL:
> >
> > ...ReportName&rs:Command=Render&rs:Format=EXCEL&rc:SimplePageHeader=True
> >
> > My motivation for using this setting was an attempt to stop the export
> > from merging several of the columns in the report since this results
> > in the error "This operation requires the merged cells to be
> > identically sized" when trying to sort on various columns within
> > Excel. My thought was that by moving the header out of the actual
> > worksheet (which is my understanding from the documentation of what
> > the setting is supposed to do), the rendered report may not need to
> > merge cells to get the output formatted properly. Any suggestions
> > would be appreciated.|||I eventually found out how to use the device info. Here are my findings:
It IS SimplePageHeaders - with an 's', plural
I used it as part of the URL when rendering directly to Excel. (I couldn't
find any way of settign this device information at design time?) The URL was
of this form
http://myserver/ReportServer?%2fTDSI%2fAssetsSummary&FxRate=1.2&rs:Command=Render&rs:Format=EXCEL&rc:SimplePageHeaders=True
This outputted my report into Excel but I think SimplePageHeaders means no
header. My original report had images and text boxes in the header (which
were admittedly causing the cell merges) but following the above the
spreadsheet does not show any of these. Is this the best I can get?
"f_mumble" wrote:
> Thanks for the follow-up, but adding the 's' didn't make a difference.
> Are my expectations of what this device info setting supposed to
> accomplish accurate?
> As a test I completely removed the header from the report, and as I
> suspected the columns are no longer merged in Excel. As a result,
> Excel is able to sort any of the columns with no problems.
> Unfortunately, having no header on the report is not an option, so any
> other suggestions are welcome.
>
> "Nico Cristache [MSFT]" <nipirvan@.microsoft.com> wrote in message news:<uFBPjyXXEHA.796@.TK2MSFTNGP10.phx.gbl>...
> > I think the device info is SimplePageHeaders.
> >
> > --
> > Nico Cristache [MSFT]
> > Microsoft SQL Server Reporting Services
> >
> > This posting is provided "AS IS" with no warranties, and confers no rights.
> >
> >
> > "f_mumble" <fred_mumble@.yahoo.com> wrote in message
> > news:5e9391dd.0406281737.724e4c66@.posting.google.com...
> > > I am trying to use the new SimplePageHeader device information setting
> > > which was introduced in RS SP1 for Excel exporting but have not seen
> > > any impact when using the setting. Following is an example of how I
> > > am using the setting in an URL:
> > >
> > > ...ReportName&rs:Command=Render&rs:Format=EXCEL&rc:SimplePageHeader=True
> > >
> > > My motivation for using this setting was an attempt to stop the export
> > > from merging several of the columns in the report since this results
> > > in the error "This operation requires the merged cells to be
> > > identically sized" when trying to sort on various columns within
> > > Excel. My thought was that by moving the header out of the actual
> > > worksheet (which is my understanding from the documentation of what
> > > the setting is supposed to do), the rendered report may not need to
> > > merge cells to get the output formatted properly. Any suggestions
> > > would be appreciated.
>

Developed one Report in Excel and want to Deploy on Report Server

I have created one SQL Server OLAP Report through Excel. I want to deploy this report on Report Server. Is it possible?

Regards,

Dinesh Patel

Unfortunately this is not a supported scenario.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

Determining Report Format from expression

I would like to be able to check format to be running as, so I can make
some columns and fields invisible if run as excel or CSV etc.
Is this possible? I dont see a way at hitting render format from Report!
object.
Thanks.On May 15, 11:55 am, Weston Weems <wweemsBLH-BLAH@.G_NOSPAM_MAIL.com>
wrote:
> I would like to be able to check format to be running as, so I can make
> some columns and fields invisible if run as excel or CSV etc.
> Is this possible? I dont see a way at hitting render format from Report!
> object.
> Thanks.
As far as I know, this functionality is not available. That said, you
can create a custom application that controls the export options and
the fields/columns that are displayed. Sorry that I could not be of
greater assistance.
Regards,
Enrique Martinez
Sr. Software Consultant|||Actually you might be onto something with that. I've already managed to
whip up my own dynamic report viewer in asp.net and it works quite
well... I will just inject a hidden parameter called format... then i
can use the format in the queries etc =)
That'll work great for me.
EMartinez wrote:
> On May 15, 11:55 am, Weston Weems <wweemsBLH-BLAH@.G_NOSPAM_MAIL.com>
> wrote:
>> I would like to be able to check format to be running as, so I can make
>> some columns and fields invisible if run as excel or CSV etc.
>> Is this possible? I dont see a way at hitting render format from Report!
>> object.
>> Thanks.
>
> As far as I know, this functionality is not available. That said, you
> can create a custom application that controls the export options and
> the fields/columns that are displayed. Sorry that I could not be of
> greater assistance.
> Regards,
> Enrique Martinez
> Sr. Software Consultant
>