Parameter Layout: Any way to specify this in report designer?

Hi,
I am designing a report with 12 parameters in 4 groups that I would
like to layout in groups of 3 parameters. I cannot find any way to
specify a layout (other than the order, which makes it confusing for
the user.
Does anyone know if there is a way to do this or if it is something
that is planned for a future version?
Many thanks
PatrickHi, Patrick
Unfortunately, the Report Server doesn't offer much control of the
parameter toolbar, except for the order in which you display your
paremeters, and whether or not to display the parameter toolbar.
If you really need to create such layout, I would recommend creating an
ASP.NET web application with an aspx page that lays out your parameters
using web controls, then you can gather the input from the user in the
postback, and create your URL to the report server, or use the SOAP API
and call the Render() method passing those params in and return the
byte[] of the rendered report in the specified format.
I know this is probably not what you wanted to hear, but people do this
all the time and you can find tons of samples onn the web.
Regards,
Thiago Silva, MCAD.NET
On Nov 22, 6:06 pm, pfisc...@.hotmail.co.uk wrote:
> Hi,
> I am designing a report with 12 parameters in 4 groups that I would
> like to layout in groups of 3 parameters. I cannot find any way to
> specify a layout (other than the order, which makes it confusing for
> the user.
> Does anyone know if there is a way to do this or if it is something
> that is planned for a future version?
> Many thanks
> Patrick|||Hi Thiago,
You got it :( - BUT thanks very much for confirming this as I know I
have not missed something that I would kick myself for!
...The thing is, it is so easy to use as it stands and that is the
beauty of it I think. It's just that much more effort to code it -> but
again thanks for the tip on samples for this - clearly others have had
a similar experience. Fingers crossed it will be improved in a future
version.
cheers Patrick
tafs7 wrote:
> Hi, Patrick
> Unfortunately, the Report Server doesn't offer much control of the
> parameter toolbar, except for the order in which you display your
> paremeters, and whether or not to display the parameter toolbar.
> If you really need to create such layout, I would recommend creating an
> ASP.NET web application with an aspx page that lays out your parameters
> using web controls, then you can gather the input from the user in the
> postback, and create your URL to the report server, or use the SOAP API
> and call the Render() method passing those params in and return the
> byte[] of the rendered report in the specified format.
> I know this is probably not what you wanted to hear, but people do this
> all the time and you can find tons of samples onn the web.
> Regards,
> Thiago Silva, MCAD.NET
> On Nov 22, 6:06 pm, pfisc...@.hotmail.co.uk wrote:
> > Hi,
> >
> > I am designing a report with 12 parameters in 4 groups that I would
> > like to layout in groups of 3 parameters. I cannot find any way to
> > specify a layout (other than the order, which makes it confusing for
> > the user.
> >
> > Does anyone know if there is a way to do this or if it is something
> > that is planned for a future version?
> >
> > Many thanks
> >
> > Patrick

Parameter is not getting defauilt value

I have a numeric parameter that does not get its default value when I deploy
the report. It works fine in report designer preview.
Is that a bug?Mark,
This behaviour is by design.
Once a report has been deployed, if you reconfigure the default value for a
particular parameter through the Report Manager then that will take
precedence over any default values that you subsequently include in the RDL
that you may re-deploy.
The rationale behind these kind of things is that the Report Administrator
is King - if the Report Administrator has manually set something on the
Report Manager to be overridden then it is not welcome that a Report
Developer comes along and overwrites such a setting.
Bill and my book gives in-depth treatment of Report Parameters on pages
283 - 292 and p286 explains the feature you are experiencing.
Best Wishes.
Peter Blackburn
Hitchhiker's Guide to SQL Server 2000 Reporting Services
www.sqlreportingservices.net
"Mark" <Mark@.discussions.microsoft.com> wrote in message
news:72E5761D-D8FA-42D4-8B03-FC7FDB83C466@.microsoft.com...
>I have a numeric parameter that does not get its default value when I
>deploy
> the report. It works fine in report designer preview.
> Is that a bug?|||What I dont understand is it's by design.
For it looks like a bug.
Let's say I have a report with a parameter that has to be entered by the user.
Later on the user decides to have a default value for that paramter.
But I cannot do it because the has entered the value for the parameter at
least once.
Am I correct?
"Peter Blackburn (www.sqlreportingservice" wrote:
> Mark,
> This behaviour is by design.
> Once a report has been deployed, if you reconfigure the default value for a
> particular parameter through the Report Manager then that will take
> precedence over any default values that you subsequently include in the RDL
> that you may re-deploy.
> The rationale behind these kind of things is that the Report Administrator
> is King - if the Report Administrator has manually set something on the
> Report Manager to be overridden then it is not welcome that a Report
> Developer comes along and overwrites such a setting.
> Bill and my book gives in-depth treatment of Report Parameters on pages
> 283 - 292 and p286 explains the feature you are experiencing.
> Best Wishes.
> Peter Blackburn
> Hitchhiker's Guide to SQL Server 2000 Reporting Services
> www.sqlreportingservices.net
>
> "Mark" <Mark@.discussions.microsoft.com> wrote in message
> news:72E5761D-D8FA-42D4-8B03-FC7FDB83C466@.microsoft.com...
> >I have a numeric parameter that does not get its default value when I
> >deploy
> > the report. It works fine in report designer preview.
> > Is that a bug?
>
>sql

Parameter Does Not Work When Deployed

This is my first attempt at using a second dataset to fill a drop-down
parameter. This works fine inside of the designer but when I deploy to the
report server, there are no values in the drop down.
I thought perhaps it was because the data source name on the server is
different. In the past I would just update it on the server after I deploy
and it worked fine. After the deploy and after chaning the DS name, I edited
the server RDL and found that not all of the DS names had been updated. I
then edited the names in the RDL and uploaded manually thinking this was the
problem but the DD list still does not work.
Thanks for any help!Are you using a shared data source? This could be a credentials problem. I
always use a shared datasource. Personally, I don't see much of a reason to
ever not use a shared data source.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Mike Harbinger" <MikeH@.Cybervillage.net> wrote in message
news:OJhRIuNjFHA.3256@.TK2MSFTNGP12.phx.gbl...
> This is my first attempt at using a second dataset to fill a drop-down
> parameter. This works fine inside of the designer but when I deploy to the
> report server, there are no values in the drop down.
> I thought perhaps it was because the data source name on the server is
> different. In the past I would just update it on the server after I deploy
> and it worked fine. After the deploy and after chaning the DS name, I
> edited the server RDL and found that not all of the DS names had been
> updated. I then edited the names in the RDL and uploaded manually thinking
> this was the problem but the DD list still does not work.
> Thanks for any help!
>|||Bruce
Thanks for your reply
Yes, I have deployed other reports to the same folder, reset them to the
same data source and it always has worked fine. What is different is this is
the first time I used a second dataset in a report (to drive the lookup drop
down). It may not be the datasource, that was just a guess on my part. Are
there othe issues that could affect a query driven lookup such that it works
in the designer but not when deployed?
Thanks
Mike
"Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
news:%23oQhumSjFHA.576@.TK2MSFTNGP15.phx.gbl...
> Are you using a shared data source? This could be a credentials problem. I
> always use a shared datasource. Personally, I don't see much of a reason
> to ever not use a shared data source.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Mike Harbinger" <MikeH@.Cybervillage.net> wrote in message
> news:OJhRIuNjFHA.3256@.TK2MSFTNGP12.phx.gbl...
>> This is my first attempt at using a second dataset to fill a drop-down
>> parameter. This works fine inside of the designer but when I deploy to
>> the report server, there are no values in the drop down.
>> I thought perhaps it was because the data source name on the server is
>> different. In the past I would just update it on the server after I
>> deploy and it worked fine. After the deploy and after chaning the DS
>> name, I edited the server RDL and found that not all of the DS names had
>> been updated. I then edited the names in the RDL and uploaded manually
>> thinking this was the problem but the DD list still does not work.
>> Thanks for any help!
>|||It could be a security issue on the database side of things. I've been
burned by that. I use one ID in development and then production is using
another one and the table/store procedure does not have the correct rights
for the production credentials. Take a look on the database at the table the
query is going against and see what the security access rights are set to.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Mike Harbinger" <MikeH@.Cybervillage.net> wrote in message
news:ulgIyGijFHA.3012@.TK2MSFTNGP12.phx.gbl...
> Bruce
> Thanks for your reply
> Yes, I have deployed other reports to the same folder, reset them to the
> same data source and it always has worked fine. What is different is this
> is the first time I used a second dataset in a report (to drive the lookup
> drop down). It may not be the datasource, that was just a guess on my
> part. Are there othe issues that could affect a query driven lookup such
> that it works in the designer but not when deployed?
> Thanks
> Mike
>
> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
> news:%23oQhumSjFHA.576@.TK2MSFTNGP15.phx.gbl...
>> Are you using a shared data source? This could be a credentials problem.
>> I always use a shared datasource. Personally, I don't see much of a
>> reason to ever not use a shared data source.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "Mike Harbinger" <MikeH@.Cybervillage.net> wrote in message
>> news:OJhRIuNjFHA.3256@.TK2MSFTNGP12.phx.gbl...
>> This is my first attempt at using a second dataset to fill a drop-down
>> parameter. This works fine inside of the designer but when I deploy to
>> the report server, there are no values in the drop down.
>> I thought perhaps it was because the data source name on the server is
>> different. In the past I would just update it on the server after I
>> deploy and it worked fine. After the deploy and after chaning the DS
>> name, I edited the server RDL and found that not all of the DS names had
>> been updated. I then edited the names in the RDL and uploaded manually
>> thinking this was the problem but the DD list still does not work.
>> Thanks for any help!
>>
>|||Bruce
The security seems ok and the main query for dataset-1 works fine. The same
data source is used for dataset-1 and dataset-2 which drives the param
drop-down list. Maybe it is not the data source since I am not getting any
erorrs. This is what happens: the the drop down list is horizontally
truncated and there are no values in displayed when you select it. It just
displays 'Select Value'.
Thanks
Mike
"Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
news:%23fTmvMijFHA.3608@.TK2MSFTNGP12.phx.gbl...
> It could be a security issue on the database side of things. I've been
> burned by that. I use one ID in development and then production is using
> another one and the table/store procedure does not have the correct rights
> for the production credentials. Take a look on the database at the table
> the query is going against and see what the security access rights are set
> to.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Mike Harbinger" <MikeH@.Cybervillage.net> wrote in message
> news:ulgIyGijFHA.3012@.TK2MSFTNGP12.phx.gbl...
>> Bruce
>> Thanks for your reply
>> Yes, I have deployed other reports to the same folder, reset them to the
>> same data source and it always has worked fine. What is different is this
>> is the first time I used a second dataset in a report (to drive the
>> lookup drop down). It may not be the datasource, that was just a guess on
>> my part. Are there othe issues that could affect a query driven lookup
>> such that it works in the designer but not when deployed?
>> Thanks
>> Mike
>>
>> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
>> news:%23oQhumSjFHA.576@.TK2MSFTNGP15.phx.gbl...
>> Are you using a shared data source? This could be a credentials problem.
>> I always use a shared datasource. Personally, I don't see much of a
>> reason to ever not use a shared data source.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "Mike Harbinger" <MikeH@.Cybervillage.net> wrote in message
>> news:OJhRIuNjFHA.3256@.TK2MSFTNGP12.phx.gbl...
>> This is my first attempt at using a second dataset to fill a drop-down
>> parameter. This works fine inside of the designer but when I deploy to
>> the report server, there are no values in the drop down.
>> I thought perhaps it was because the data source name on the server is
>> different. In the past I would just update it on the server after I
>> deploy and it worked fine. After the deploy and after chaning the DS
>> name, I edited the server RDL and found that not all of the DS names
>> had been updated. I then edited the names in the RDL and uploaded
>> manually thinking this was the problem but the DD list still does not
>> work.
>> Thanks for any help!
>>
>>
>

Parameter

Hi all:
I am new in RS. I use Report Designer to create a report and use Report
Manger to view it. My question is I want to use parameter passing to let the
end-user to select multiple item in the parameter list, however, by using
Report Designer the parameter list only alow user to select one item. Anyone
know the good solution for this problem.
Thanks,
KentKent,
Version 1.0 of Reporting Services doesn't support multi-value parameters. As
a workaround, consider building your own front end to support multi
selection. Once this is in place, you can make your report query expression
based, e.g. by using the SQL IN clause.
--
Hope this helps.
----
Teo Lachev, MCSD, MCT
Author: "Microsoft Reporting Services in Action"
Publisher website: http://www.manning.com/lachev
Buy it from Amazon.com: http://shrinkster.com/eq
Home page and blog: http://www.prologika.com/
----
"kent kent" <kentkent@.discussions.microsoft.com> wrote in message
news:7FC417C5-078E-433D-98BF-C511EAB28D9A@.microsoft.com...
> Hi all:
> I am new in RS. I use Report Designer to create a report and use
Report
> Manger to view it. My question is I want to use parameter passing to let
the
> end-user to select multiple item in the parameter list, however, by using
> Report Designer the parameter list only alow user to select one item.
Anyone
> know the good solution for this problem.
> Thanks,
> Kent
>

Page Size

Hi,
How can I define Page Size.Orientation in Report Designer?
I am looking for some way to define letter/legal size paper and also
Landescap/Portrate paper orientation.
Can users change those printig attributes when they are printing/expoting
that to PDF file?
Thank,
AlanYou can change the page width and page height to 11 x 8.5 instead of 8.5 x
11 inches in the report designer. You can find these properties in the
Report | "Report Properties..." menu item, select the Layout tab.
A user can change the Rendering attributes when they view a report via the
ReportServer web service. For example, to retrieve a PDF report rendered
with a height of 15 inches instead of the default 11 inches, a user would
use this URL:
http://servername/ReportServer?/Project1/Test_Report1&rs:Command=Render&rs:F
ormat=PDF&rc:PageHeight=15in
The user's printer settings is up to them but it would look best if the
rendering parameters match the printer parameters. For more information
see the Reporting Services Device Information Settings page on MSDN:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/RSPROG/htm/
rsp_prog_soapapi_dev_5l7q.asp?frame=true
Jonathan Kyle, MCSD
Microsoft WebData Support Engineer
This posting is provided "AS IS" with no warranties, and confers no rights.
--
>From: "A.M" <nospam1@.online.nospam>
>Subject: Page Size
>Date: Tue, 7 Sep 2004 13:42:04 -0400
>Lines: 14
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-Newsreader: Microsoft Outlook Express 6.00.2800.1437
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
>Message-ID: <#MFqkGQlEHA.3520@.TK2MSFTNGP11.phx.gbl>
>Newsgroups: microsoft.public.sqlserver.reportingsvcs
>NNTP-Posting-Host: 209.226.40.154
>Path:
cpmsftngxa10.phx.gbl!TK2MSFTFEED01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP11

Page Setup disabled in Report Designer

I'm trying to change the snap-to grid functionality in a SRS 2005 Report Design (within VS 2005). I tried the same steps in the following post, without success. Based on the SRS help, it appears you change Grid Settings by accessing the File > Page Setup dialog, but the Page Setup (along with Print) is disabled.

Maybe these are instructions for Report Builder only? If so, how do you adjust the Grid Settings (to turn off the "snap" functionality) for a SRS Report project in Visual Studio?

Thanks,

Michael

Hello Michael,

From the Report menu, select Report Properties, then in the General tab, uncheck the 'Snap to grid' checkbox.

Hope this helps.

Jarret

|||

Jarret,

That was so easy!

I thought I was seeing all the available properties by right-clicking on the report and selecting 'Properties'.

Great help!

Thanks,
Michael