Delete Column Problems

I created a report with say 5 columns, then decide I only want 4 of them.
My approach was:
1) go to data area and remove from query
2) go to Layout Tab and remove from display
But when I preview it - I get error - it still seems to always be looking
for the column I deleted - what can I do?make sure there are no referneces to that column or field thru any filters
or the where statement in the data area.
"Joe" <hortoristic@.gmail dot com> wrote in message
news:eAINil6yGHA.4648@.TK2MSFTNGP04.phx.gbl...
>I created a report with say 5 columns, then decide I only want 4 of them.
> My approach was:
> 1) go to data area and remove from query
> 2) go to Layout Tab and remove from display
> But when I preview it - I get error - it still seems to always be looking
> for the column I deleted - what can I do?
>|||Go to DataSet,Go to Fields,remove the unwanted column.it should work
fine now
Regards
Raj Deep.A
Ben Watts wrote:
> make sure there are no referneces to that column or field thru any filters
> or the where statement in the data area.
> "Joe" <hortoristic@.gmail dot com> wrote in message
> news:eAINil6yGHA.4648@.TK2MSFTNGP04.phx.gbl...
> >I created a report with say 5 columns, then decide I only want 4 of them.
> >
> > My approach was:
> > 1) go to data area and remove from query
> > 2) go to Layout Tab and remove from display
> >
> > But when I preview it - I get error - it still seems to always be looking
> > for the column I deleted - what can I do?
> >sql

Delegation And Windows 2003

I have the following scenario:
Machine 1: IIS Server - running Reporting Services
Machine 2: SQL Server - stores all data that a report will use
These servers run in a Windows 2000 Active Directory domain.
The IIS web site has the directory security set to Windows authentication
and Anonymouse authentication unchecked.
The reports use a shared data source that has the Windows authentication
checkbox checked.
The IIS Server has the delegation checkbox checked in Active Directories and
Users.
Run the report from a browser and get the login failed for the anonymous
user. Run the report from the IIS Server and it works. This is a sure
indication of a delegation issue.
What am I missing?Hi,
From your descriptions, I understood that running the report from a browser
and get the login failed for the anonymous user. Run the report from the
IIS Server and it works. Have I understood you? Correct me if I was wrong.
Based on my socpe, it seems to be a Kerberos issue and the simplest
workaround is changing the shared data source to use SQL authentication to
the SQL Server.
To set up delegation on a computer, the following conditions must be met:
* The account doing the delegation must be set to Trusted for delegation to
any service or Trusted for delegation to specified services only.
* The account that the service is delegating for must not have the Account
is sensitive and cannot be delegated option chosen.
* An administrator must have the Enable computer and user accounts to be
trusted for delegation privilege on the computer in order to enable
delegation.
See the following knowledge base article for more detailed information
Basic Overview of Kerberos User Authentication Protocol in Windows 2000
http://support.microsoft.com/kb/217098
Thank you for your patience and corporation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Online Partner Support Specialist
Partner Support Group
Microsoft Global Technical Support Center
---
Get Secure! - http://www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!sql

Defualt Value Question?

Hi,everyone
I have a report.
I List a employees in a table,I use a parameter "DepartmentID"(0-n) to
query employees dataset1.
I have other dataset2 ,the department from a sql text.
the parameter "departmentId" from dataset2,and I need a default value
"All" to list all employees.
But the default value not work.
RedmoonIf you use available values, they should include possible default value (in
your case "All'). If default value does not match any of available values it
is rejected.
--
Lev
http://blogs.msdn.com/levs
This posting is provided "AS IS" with no warranties, and confers no rights.
"Redmoon" <heavenwing@.163.com> wrote in message
news:Xns952DBA9506D1Fheavenwing163com@.207.46.248.16...
> Hi,everyone
> I have a report.
> I List a employees in a table,I use a parameter "DepartmentID"(0-n) to
> query employees dataset1.
> I have other dataset2 ,the department from a sql text.
> the parameter "departmentId" from dataset2,and I need a default value
> "All" to list all employees.
> But the default value not work.
> Redmoon

defining style

is there a way to set the style of a report project in sql server 2005
reporting services? im getting really tired of having to change the fonts,
colors, etc. for every new report i make.On Jul 19, 6:13 pm, "JTL" <j...@.clickstreamtech.com> wrote:
> is there a way to set the style of a report project in sql server 2005
> reporting services? im getting really tired of having to change the fonts,
> colors, etc. for every new report i make.
For the most part, there is not much control over the style available
for reports. That said, these links might be helpful somewhat.
http://msdn2.microsoft.com/en-us/library/ms345247.aspx
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=83322&SiteID=1
Hope this helps.
Regards,
Enrique Martinez
Sr. Software Consultant|||Hi JTL,
what you can do is create a sample / mockup report that has all the style
elements you want in it (e.g. also headers/footers,fonts/colours/pre-defined
tables..etc). Then you save this as a report in the template directory. Each
time you now want to design a new report, you just select that template et
voila.. bob's your uncle... It's then only a matter of deleting the items
(e.g. table) if you don't want to use it in the new report... (well at least
that's how I do it!).
hope it helps,
mischa
"JTL" wrote:
> is there a way to set the style of a report project in sql server 2005
> reporting services? im getting really tired of having to change the fonts,
> colors, etc. for every new report i make.
>
>

Defining sort order using parameter fields.

Hi!

This is my first post at this forum.

I have a parameterfield wich the users can use to enter sortorder to the report. I have then created a formula with this code in it.

if {?sortid} = "1" then ({DMD_VIEW_ERRAND.er_control_date} AND {DMD_VIEW_ERRAND.er_id})
else
if {?sortid} = "2" then ({DMD_VIEW_ERRAND.er_activity_desc} AND {DMD_ERRAND.ER_HANDLERDATA} AND {DMD_VIEW_ERRAND.er_id})


This formula is then added into the record sorting expert.

The problem is there is an error in the formula. I want to order by multiple columns. Is it possible?
If it is, what's wrong with my code?

I'm using crystal XI
Best regards
HeleniusI've solved it.

Here's the code

if {?sortid} = "1" then (CStr({DMD_VIEW_ERRAND.er_control_date_fmt}) + "AND" + {DMD_VIEW_ERRAND.er_id})
else
if {?sortid} = "2" then ({DMD_VIEW_ERRAND.er_activity_desc} + "AND" + {DMD_ERRAND.ER_HANDLERDATA} + "AND" + CStr({DMD_VIEW_ERRAND.er_control_date_fmt}) + "AND" + {DMD_VIEW_ERRAND.er_id})

I had a little convertion problem...

/Helenius|||Noooo, it doesn't seem to be solved after all. The report only sort based by the first column. Any suggestions??

Defining dataset query in vb.net

Hi all,
there are lots of objects about defining the report data source ,data set,
query etc.
but is there any examples of defining them and assign to a report?
i feel confuse cos i dun quite know how to use them.(i want to construct the
Query in web form first then pass to the report.)
thanks in advance!hi all,
may be i should post my questions clearly,
i know how to assign a datasource to the report using setreportdatasource(),
but|||BUT
HOW TO ASSIGN A DATASET TO A DATASOURCE, AND
HOW TO ASSIGN A QUERY TO A DATASET?
i dun know if my concept is corroect or not, please let me know if i have
said something wrong
thanks in advance.|||Two points. First, the way you are envisioning it today can not easily be
done. People do this but it is not an out of the box experience. By that I
mean, it is not a built in capability but it is possible to use the
extensions and write your own data extension to do this.
The way it is really designed today is for you to create the reports and the
dataset from within Reporting Services. The name matches the design. It is
designed to be a service that you can invoke. You can use the product three
ways. First, it ships with its own portal. This is the quickest way to use
it and is the best way to at least get your feet wet. Then you can integrate
with your own web app by using either URL integration (your app creates the
URL string passing any parameters). You can also integrate with soap (web
services).
Version 2 (Yukon and Widbey) will come with new controls that should allow
you to do this more the way you are envisioning: create a recordset and
passing it to the control. There will be both a winform and a webform
control.
Bruce L-C
"Jasonymk" <Jasonymk@.discussions.microsoft.com> wrote in message
news:D4798A3A-E8D1-4A8E-9DD2-14E8A9725B6E@.microsoft.com...
> BUT
> HOW TO ASSIGN A DATASET TO A DATASOURCE, AND
> HOW TO ASSIGN A QUERY TO A DATASET?
> i dun know if my concept is corroect or not, please let me know if i have
> said something wrong
> thanks in advance.|||thank you so much bruce,
Does it mean that what i can do for the time being is just passing
paramenters to the query built in the rs designer, not passing a query to a
dataset?
"Bruce Loehle-Conger" wrote:
> Two points. First, the way you are envisioning it today can not easily be
> done. People do this but it is not an out of the box experience. By that I
> mean, it is not a built in capability but it is possible to use the
> extensions and write your own data extension to do this.
> The way it is really designed today is for you to create the reports and the
> dataset from within Reporting Services. The name matches the design. It is
> designed to be a service that you can invoke. You can use the product three
> ways. First, it ships with its own portal. This is the quickest way to use
> it and is the best way to at least get your feet wet. Then you can integrate
> with your own web app by using either URL integration (your app creates the
> URL string passing any parameters). You can also integrate with soap (web
> services).
> Version 2 (Yukon and Widbey) will come with new controls that should allow
> you to do this more the way you are envisioning: create a recordset and
> passing it to the control. There will be both a winform and a webform
> control.
> Bruce L-C
> "Jasonymk" <Jasonymk@.discussions.microsoft.com> wrote in message
> news:D4798A3A-E8D1-4A8E-9DD2-14E8A9725B6E@.microsoft.com...
> > BUT
> > HOW TO ASSIGN A DATASET TO A DATASOURCE, AND
> > HOW TO ASSIGN A QUERY TO A DATASET?
> >
> > i dun know if my concept is corroect or not, please let me know if i have
> > said something wrong
> >
> > thanks in advance.
>
>|||by the way, could you please explain more about the method you suggest?
as i really have to make a dynamic query string (not just for the data
value, also the whole query)|||RS has a lot of flexibility in how the query is designed. You can have query
parameters (which map to report parameters). You can refer to global
variable (for instance user!userid), you can base the query on an expression
(expressions are very powerful so there is a whole lot you can do once you
do that).
I think before you jump all the way to where you want to end up you should
play around with it a little bit so you understand the capabilities. Create
a few simple reports, have a query parameter, try out a simple query based
on an expression.
After you understand the capabilities you can decide if it meets your needs.
As I said you can integrate with URL if you want to have your own web site
or you can also use a very full featured web services (soap). Then there are
also extentions possible (data extensions, security extensions).
Bruce L-C
"Jasonymk" <Jasonymk@.discussions.microsoft.com> wrote in message
news:131AC930-6A8F-497B-9E0B-D5CD0B554FF1@.microsoft.com...
> by the way, could you please explain more about the method you suggest?
> as i really have to make a dynamic query string (not just for the data
> value, also the whole query)|||Thanks a lot Bruce,
you said by expression, do you mean by SQL command?
my situation is like this , i use the Render() function to generate reports
with the query "SELECT * FROM table WHERE value=@.parameter" in the report
project, i have tried to pass the parameter to the query by inputting it to
the render function.
thats the most i can do, but the parameters are only limited to a value, not
a clause(esp WHERE clause)...what if i wanna get the data with "WHERE value2
= @.para2 AND value3 =@.para3"'
will URL solve my problem? i have found a method , which is about editing
the rdl (xml)file in vb...but then i will have to edit the whole rdl file.
"Bruce Loehle-Conger" wrote:
> RS has a lot of flexibility in how the query is designed. You can have query
> parameters (which map to report parameters). You can refer to global
> variable (for instance user!userid), you can base the query on an expression
> (expressions are very powerful so there is a whole lot you can do once you
> do that).
> I think before you jump all the way to where you want to end up you should
> play around with it a little bit so you understand the capabilities. Create
> a few simple reports, have a query parameter, try out a simple query based
> on an expression.
> After you understand the capabilities you can decide if it meets your needs.
> As I said you can integrate with URL if you want to have your own web site
> or you can also use a very full featured web services (soap). Then there are
> also extentions possible (data extensions, security extensions).
> Bruce L-C
> "Jasonymk" <Jasonymk@.discussions.microsoft.com> wrote in message
> news:131AC930-6A8F-497B-9E0B-D5CD0B554FF1@.microsoft.com...
> > by the way, could you please explain more about the method you suggest?
> >
> > as i really have to make a dynamic query string (not just for the data
> > value, also the whole query)
>
>|||My suggestion is to back up and first learn the capabilities of Reporting
Services before you start doing integration work. Spend a little time
experimenting. Do some sample reports. Although you can edit RDl and deploy
when you deploy it it will be accesible to all users so you would have to
come up with a unique naming scenario. Plus you have the performance hit of
deploying every time the user requests the report.
Read up on dynamic SQL. Read up and play with expressions and make sure you
understand the power of expressions. Be sure you understand the difference
between query parameter and report parameter. Read up and try a creating a
url to pass a simple parameter to a report. Then get into creating a dynamic
query.
And no, an expression is not a SQL command. It will evaluate to an sql
command but it can have iif statements, nested iif statements etc so you can
create a SQL command with a varying amount of clauses in the where command.
So far I have not heard anything you are trying to do that requires editing
the rdl file directly or writing a data extension. Custom assemblies are
also possible but again, in most cases are not necessary. I write a little
code behind but have found that normally an expression solves my needs.
Bruce L-C
MVP Reporting Services
Again, you are jumping to fast to the end result without first learning
Reporting Services.
"Jasonymk" <Jasonymk@.discussions.microsoft.com> wrote in message
news:ECCC7777-8D8D-42A4-80FB-EB84CA933851@.microsoft.com...
> Thanks a lot Bruce,
> you said by expression, do you mean by SQL command?
> my situation is like this , i use the Render() function to generate
> reports
> with the query "SELECT * FROM table WHERE value=@.parameter" in the report
> project, i have tried to pass the parameter to the query by inputting it
> to
> the render function.
> thats the most i can do, but the parameters are only limited to a value,
> not
> a clause(esp WHERE clause)...what if i wanna get the data with "WHERE
> value2
> = @.para2 AND value3 =@.para3"'
> will URL solve my problem? i have found a method , which is about editing
> the rdl (xml)file in vb...but then i will have to edit the whole rdl file.
>
> "Bruce Loehle-Conger" wrote:
>> RS has a lot of flexibility in how the query is designed. You can have
>> query
>> parameters (which map to report parameters). You can refer to global
>> variable (for instance user!userid), you can base the query on an
>> expression
>> (expressions are very powerful so there is a whole lot you can do once
>> you
>> do that).
>> I think before you jump all the way to where you want to end up you
>> should
>> play around with it a little bit so you understand the capabilities.
>> Create
>> a few simple reports, have a query parameter, try out a simple query
>> based
>> on an expression.
>> After you understand the capabilities you can decide if it meets your
>> needs.
>> As I said you can integrate with URL if you want to have your own web
>> site
>> or you can also use a very full featured web services (soap). Then there
>> are
>> also extentions possible (data extensions, security extensions).
>> Bruce L-C
>> "Jasonymk" <Jasonymk@.discussions.microsoft.com> wrote in message
>> news:131AC930-6A8F-497B-9E0B-D5CD0B554FF1@.microsoft.com...
>> > by the way, could you please explain more about the method you suggest?
>> >
>> > as i really have to make a dynamic query string (not just for the data
>> > value, also the whole query)
>>|||thank you so much bruce,
after a day's study, i start to understand now, and i think nested iif maybe
the direction that i am heading to~~~
thank you sooo much for showing me the way!
"Bruce Loehle-Conger" wrote:
> My suggestion is to back up and first learn the capabilities of Reporting
> Services before you start doing integration work. Spend a little time
> experimenting. Do some sample reports. Although you can edit RDl and deploy
> when you deploy it it will be accesible to all users so you would have to
> come up with a unique naming scenario. Plus you have the performance hit of
> deploying every time the user requests the report.
> Read up on dynamic SQL. Read up and play with expressions and make sure you
> understand the power of expressions. Be sure you understand the difference
> between query parameter and report parameter. Read up and try a creating a
> url to pass a simple parameter to a report. Then get into creating a dynamic
> query.
> And no, an expression is not a SQL command. It will evaluate to an sql
> command but it can have iif statements, nested iif statements etc so you can
> create a SQL command with a varying amount of clauses in the where command.
> So far I have not heard anything you are trying to do that requires editing
> the rdl file directly or writing a data extension. Custom assemblies are
> also possible but again, in most cases are not necessary. I write a little
> code behind but have found that normally an expression solves my needs.
> Bruce L-C
> MVP Reporting Services
> Again, you are jumping to fast to the end result without first learning
> Reporting Services.
> "Jasonymk" <Jasonymk@.discussions.microsoft.com> wrote in message
> news:ECCC7777-8D8D-42A4-80FB-EB84CA933851@.microsoft.com...
> > Thanks a lot Bruce,
> >
> > you said by expression, do you mean by SQL command?
> >
> > my situation is like this , i use the Render() function to generate
> > reports
> > with the query "SELECT * FROM table WHERE value=@.parameter" in the report
> > project, i have tried to pass the parameter to the query by inputting it
> > to
> > the render function.
> >
> > thats the most i can do, but the parameters are only limited to a value,
> > not
> > a clause(esp WHERE clause)...what if i wanna get the data with "WHERE
> > value2
> > = @.para2 AND value3 =@.para3"'
> >
> > will URL solve my problem? i have found a method , which is about editing
> > the rdl (xml)file in vb...but then i will have to edit the whole rdl file.
> >
> >
> >
> > "Bruce Loehle-Conger" wrote:
> >
> >> RS has a lot of flexibility in how the query is designed. You can have
> >> query
> >> parameters (which map to report parameters). You can refer to global
> >> variable (for instance user!userid), you can base the query on an
> >> expression
> >> (expressions are very powerful so there is a whole lot you can do once
> >> you
> >> do that).
> >>
> >> I think before you jump all the way to where you want to end up you
> >> should
> >> play around with it a little bit so you understand the capabilities.
> >> Create
> >> a few simple reports, have a query parameter, try out a simple query
> >> based
> >> on an expression.
> >>
> >> After you understand the capabilities you can decide if it meets your
> >> needs.
> >> As I said you can integrate with URL if you want to have your own web
> >> site
> >> or you can also use a very full featured web services (soap). Then there
> >> are
> >> also extentions possible (data extensions, security extensions).
> >>
> >> Bruce L-C
> >>
> >> "Jasonymk" <Jasonymk@.discussions.microsoft.com> wrote in message
> >> news:131AC930-6A8F-497B-9E0B-D5CD0B554FF1@.microsoft.com...
> >> > by the way, could you please explain more about the method you suggest?
> >> >
> >> > as i really have to make a dynamic query string (not just for the data
> >> > value, also the whole query)
> >>
> >>
> >>
>
>

Defining custom column groups on a matrix report in report builder

I have table called Buildings which has market and sq. ft information.
I want to create a matrix report that has the market as the row group and
sq. ft ranges as the column group and shows the # of buildings in each
market that fall in the sq. ft ranges.
Sq. ft ranges are 0-5000, 5001-10000 etc...
My questions is a) is this something that can be done using report builder
b) how do i define the sq. ft ranges
c) how do I find the count of buildings whose sq. footage falls within the
range.
ThanksOn Nov 14, 1:18 pm, "shikarishambu" <shikarishamb...@.hotmail.com>
wrote:
> I have table called Buildings which has market and sq. ft information.
> I want to create a matrix report that has the market as the row group and
> sq. ft ranges as the column group and shows the # of buildings in each
> market that fall in the sq. ft ranges.
> Sq. ft ranges are 0-5000, 5001-10000 etc...
> My questions is a) is this something that can be done using report builder
> b) how do i define the sq. ft ranges
> c) how do I find the count of buildings whose sq. footage falls within the
> range.
> Thanks
A) Yes
B) In your Datasets window, right-click on the name of the dataset and
Add a new field. Call it "Sq Foot Range" and make it a calculated
field. Use an expression like
= Fields!SqFoot.Value - Fields!SqFoot.Value Mod 5000
Since you are shifting your range to include the evenly divided number
in the lower group, you really want
= CStr( ( (X-1) - (X-1) Mod 5000 ) + 1 ) & " to " & CStr( ( (X-1) -
(X-1) Mod 5000 ) + 5000 )
C) Create a Matrix with a Market in the Row Group, Sq Foot Range in
the Column Group, and Count( Fields!SqFoot.Value ) in the Details.
Hope that helps.
-- Scott

defining background color in matrix

Hi All
In my report there is a dynamic matrix.
two section inside the data region need to be paint in two different
color.
i defined an Expression in the background properties.
the Expression define two ranges(four cordinates) in order to paint one
section
and more two ranges for the other section.
the problem occour while examine the data come from the DB. in those
junction
that there was no data involve the cell was'nt paint although it is in
the
range
of the painting.
i try to solve this by using the " is nothing" function but without any
successes.
one solution i had which is works was declaring temporary table int he
procedure ,addind rows to the temporary table plus the data it self
while
running
and then in the report to blank those cells by filter them.it work's
paint
those cells but damage the subtotal line(because new rows were adding
to the
table source).
if any knows how to solve this conflic i will very much appreciate
this.
thanks in advanced
Amir KrugliakHi
If this is reporting services then you may be better off posting to the
microsoft.public.sqlserver.reportingsvcs newsgroup.
John
"amir.krugliak@.gmail.com" wrote:

> Hi All
> In my report there is a dynamic matrix.
> two section inside the data region need to be paint in two different
> color.
> i defined an Expression in the background properties.
> the Expression define two ranges(four cordinates) in order to paint one
> section
> and more two ranges for the other section.
> the problem occour while examine the data come from the DB. in those
> junction
> that there was no data involve the cell was'nt paint although it is in
> the
> range
> of the painting.
> i try to solve this by using the " is nothing" function but without any
> successes.
> one solution i had which is works was declaring temporary table int he
> procedure ,addind rows to the temporary table plus the data it self
> while
> running
> and then in the report to blank those cells by filter them.it work's
> paint
> those cells but damage the subtotal line(because new rows were adding
> to the
> table source).
> if any knows how to solve this conflic i will very much appreciate
> this.
> thanks in advanced
> Amir Krugliak
>

Define Printer in Report

I have a client who tells me in Access you could assign the printer directly to the report using PrtDevNames and PrtDevMode. Apparently it's true.

Can this be done in Reporting Services?

check out the section "Direct Client Printing" in this link:

http://www.microsoft.com/technet/prodtechnol/sql/2005/2005ssrs.mspx

Shyam

|||

Thank you for the response.

Although that is a nice feature in 2005 over 2000. It's not quite what I am looking for I don't think.

I want to be able to store which printer the report should be sent to when printed so the user does not have to, I am looking for the same functionality that is in Access I mentioned above.

define default for date report parameter / analysis services

I have a report which will one day display some data from an analysis services cube. my first step is to create a drop down parameter enabling the user to choose the date. I'd like to display only dates that have data, and I'd like it to default to today.

So I've created a dataset that will be the datasource for the dropdown displaying the available non-empty dates, which works fine.

SELECT measures.turnover ON COLUMNS,

nonempty([TBL DIM DATE].[DATE_ONLY].[DATE_ONLY].ALLMEMBERS ) ON ROWS

FROM [Itdev1 Hk]

I've also set the report parameter up to be a queried paramter,and to use the above dataset as it source, with [DATE_ONLY] displayed. and [DATE_ONLY] as the value.

Now, how do I get it to default to the last valid member in the list?

I presume you are trying to have the latest date selected by default? If so, return your dataset in descending order (do an ORDER(<set>, DESC) on the rows), so that your latest date is at the top of the list.

|||this is helpful since now when I click the drop down the most likely values for me to use are at the top. but it has not caused any value to be selected by default.
|||You can use the same dataset in the default value query, which seems to collapse to the first row returned. I have no idea what the implications of doing this are, I happened on it by accident.|||

this is a helpful tip!

|||

i;m attempting to order by date in descending order. but it seems to sort in a random order when I do this ....

SELECT NON EMPTY { [Measures].[TURNOVER - WM INTERDAY] } ON COLUMNS, NON EMPTY { order([Time].[Date].[Date].ALLMEMBERS, [Time].[Date], desc ) } DIMENSION PROPERTIES MEMBER_CAPTION, MEMBER_UNIQUE_NAME ON ROWS FROM [Itdev1 Hk] CELL PROPERTIES VALUE, BACK_COLOR, FORE_COLOR, FORMATTED_VALUE, FORMAT_STRING, FONT_NAME, FONT_SIZE, FONT_FLAGS

and then in alphabetical order when I sort like this

SELECT NON EMPTY { [Measures].[TURNOVER - WM INTERDAY] } ON COLUMNS, NON EMPTY { order([Time].[Date].[Date].ALLMEMBERS, [Time].[Date].MemberValue, desc ) } DIMENSION PROPERTIES MEMBER_CAPTION, MEMBER_UNIQUE_NAME ON ROWS FROM [Itdev1 Hk] CELL PROPERTIES VALUE, BACK_COLOR, FORE_COLOR, FORMATTED_VALUE, FORMAT_STRING, FONT_NAME, FONT_SIZE, FONT_FLAGS

how do I get it to sort by real date?

Defaulting the export option

Is there a way to control the contents of the report export drop down
list? Specifically, I would like to set a default export to PDF
(instead of the "Select a format" entry)You can force the rendering format for that report but I don't think there is
a way to default the drop-down selection.
Here is a PDF render format against the AdventureWorks sample reports (the
report gets generated in PDF):
//localhost/ReportServer?/AdventureWorks Sample Reports/Company
Sales&rs:Format=PDF&rs:Command=Render
"Paul" wrote:
> Is there a way to control the contents of the report export drop down
> list? Specifically, I would like to set a default export to PDF
> (instead of the "Select a format" entry)

Defaulting Start and End dates to the previous month.

I have two parameters in my report (StartDate and EndDate). I want to default these parameters to the previous month.

For example... If today is 5/17/2007, I want StartDate to be 4/1/2007 and EndDate to be 4/30/2007. If today would be January 30th 2007, I would want StartDate to be 12/1/2006 and EndDate to be 12/31/2006.

How can I do this?

Nevermind... I used the following two functions. However, if you know of a better way to do this, please let me know.

Public Function EndDt() As Date

Dim Today As Date = Date.Today

Dim Day As Integer = Today.Day

Dim EndDate As Date

EndDate = Today.AddMonths(1)

EndDate = Today.AddDays(-Day)

Return EndDate

End Function

Public Function StartDt() As Date

Dim Today As Date = Date.Today

Dim Day As Integer = Today.Day - 1

Dim StartDate As Date

StartDate = Today.AddMonths(-1)

StartDate = Today.AddDays(-Day)

Return StartDate

End Function

|||

I can't think of a quick direct way

but I do want to suggest using BETWEEN, and first of month (so that you don't have to worry about # of days in a month)

e.g. for 05/17/2007

you'd want SQL code to be

Code Snippet

column BETWEEN 04/01/2007 AND 05/01/2007

since BETWEEN is inclusive, but only up to '05/01/2007 00:00:00', anything after 05/01/2007 midnight will NOT show up

so in backend SQL

it'll be like

Code Snippet

SELECT
previous_month = CAST( MONTH(getdate())-1 AS varchar) + '/01/' + CAST(YEAR(getdate()) AS varchar)
, current_month = CAST( MONTH(getdate()) AS varchar) + '/01/' + CAST(YEAR(getdate()) AS varchar)

then you get

previous_month current_month

4/01/2007 5/01/2007

Defaulting Parameters based on time of day?

I need to set up some parameters which are based on the time of day. For instance, night shift vs/ day shift. If I run the report during the day, default to the day shift criteria (5 am to 5 pm), and likewise for the night shift (5 pm to 5 am). On the night shift, I also need to accomodate for the change in dates as well. Is this even possible in a single report? HELP!!

Thanks!

Does it really need to be parameters, or could you just check the time in your SQL or report code?

Defaulting Date Parameter

Hello,

I have a report parameter StartDate. Properties are

DataTypeataTime

Prompt: StartDate

Default Values:

Non Queried : =NOW()

I set the default value to Now(). When I go to preview, the StartDate parameter is blank and its been locked & grayed out. I also tried

Today() and Globals!SystemTime but that does not work either. Is there any other solution to make this work?

Thanks

Raj

I have not seen any responses on this. Wanted to see if there are any ideas/ thoughts on this.|||

Try:

Code Snippet

=cDate(FormatDateTime(Now, DateFormat.ShortDate))

Larry|||HI,
You can give the following expression for the default value of startdate;
DateValue(now()).

Cheers,
Shri|||

Is this the only parameter in your report? If it is, then you shouldn't be having any problems.

If not, try entering the values for all the parameters that come before StartDate. Then you should be able to see the default value & it should not be greyed out any more.

-Aayush

Default View

Is there a way to change the default view of a report to be PDF instead of the HTML View when a report is launched? I would also like to supress the parameters of the report - Can someone tell me if this is possible and possibly point me in the direction of more information on this ?

ThanxYeah we can chage it.
one exapmle is by unig url

Likein url
/ReportServer?/samplereports/abc&rs:Command=Render&rs:Format=HTML4.0&rc:Parameters=false

just change the format =HTML4.0 to
Format=PDF

It will automatically open PDF file likewise for others|||Thank You for the quick response - this will do the trick!

Thanx again

Default Values not Selected on Report Manager

I have a report with quite a few parameters, both multivalue and single, all populated from a query. In the Report Designer I have set up default values and everything works great. When I deploy these reports the default values are not being set. Am I missing a step?It's a SQL report or an MDX report?

In the report manager when you choose the parameters and execute the report. It's rendered fine?|||

The server has behavior that it keeps the old parameter defaults that are set, even after republishing. Try deleting the report and republishing.

|||I have not seen the Report Server maintain default parameter values when a report is redeployed. After redeploying the report I have to manually reset the defaults (Properties tab --> Parameters page --> Override Default button).

If there is some property of the server that would persist the defaults between deployments, I'd love to learn about it. Thanks.

Default values in a parameter problem

We have a report that has about five different parameters. One of the parameters is a float value and we have a default value set at 999,999,999.00 and the report parameter accepts this value. The other parameter (a string) has a default value set at 0, however it is not showing up in the textbox for that parameter. The parameter is non-queried and is just a report parameter.

When we preview the report, it is there. Once we deploy the report to the report server, it is not. Now, the development machine is using SP2, but the Report Server is still at SP1. Could this be the problem? If it is, why would the float default value display and the string default value not?

Thanks for the information.

What is the expression you use to set the default value (the one that isn't working)?|||The expression that we are using is =0. We also tried ="0".|||

Could be a simple problem of the RDL file not getting refreshed preoperly in the Report Server. Try deleting the existing RDL file and deploying it again.

Just a thought

-Aayush

|||Thanks, we will try that.|||

I agree, as we run into issues at times to, where I have to delete and re-deploy

or sometimes if I'm lazy, I just modify the parameter on Report Server report page (tab "Parameters" on the left, under "Properties")

FYI 0 is right for default parameter, not "0"

Default values for report parameters gets lost in Report Server

I have a report which takes few parameters. I have set some defalut value for
them. The default values work good when i Preview teh report. But when i
deploy the report to the Report Server, the default values get lost and the
user has to type them all again. Any clue on how to solve this issue?I think you can try setting the default value in VS (designer) as
="Yes" instead of Yes
see if that works.
That being said, I am having some difficulty because it appears setting
things in the designer (for parameters) and setting parameter properties on
RS behaves in different ways. The prompt user, prompt string, default value
etc. seems to not be communicating clearly with what was set in the
designer. Example - if you have a date parameter, and in the designer you
set the default to be =Left(today, 10) - an expression, in other words - when
you go to look in RS and tweak the parameter properties it has default value
checked, but it does not sjow the expression and it doesn't see any valid
default value - and gives an error.
"anandr" wrote:
> I have a report which takes few parameters. I have set some defalut value for
> them. The default values work good when i Preview teh report. But when i
> deploy the report to the Report Server, the default values get lost and the
> user has to type them all again. Any clue on how to solve this issue?|||The reason you aren't seeing any value in the Default Value box is because
your default value is an expression. The Default Value textbox on the
Parameters property page only displays default values when they are strings
and not expressions (this does not mean that you do not have a default value
when it is an expression). The reason you might be getting an error is if
your parameter type is date, you're returning a string instead of a date. I
don't know what your parameter type is, but it is just a thought. Hope that
helps you a bit.
David
"Myles" wrote:
> I think you can try setting the default value in VS (designer) as
> ="Yes" instead of Yes
> see if that works.
> That being said, I am having some difficulty because it appears setting
> things in the designer (for parameters) and setting parameter properties on
> RS behaves in different ways. The prompt user, prompt string, default value
> etc. seems to not be communicating clearly with what was set in the
> designer. Example - if you have a date parameter, and in the designer you
> set the default to be =Left(today, 10) - an expression, in other words - when
> you go to look in RS and tweak the parameter properties it has default value
> checked, but it does not sjow the expression and it doesn't see any valid
> default value - and gives an error.
>
> "anandr" wrote:
> > I have a report which takes few parameters. I have set some defalut value for
> > them. The default values work good when i Preview teh report. But when i
> > deploy the report to the Report Server, the default values get lost and the
> > user has to type them all again. Any clue on how to solve this issue?|||Thanks David -
actually, the parm type is a string - I believe that is the only way
something like
=Left(today, 10) would work, because it is a string function (basically).
It is trying, though, when you open up the parameters page of the properties
tab on http://<Server>/Reports and fiddle with a completely different
parameter and try to apply the changes, that it gives you the error on any
string type parameter that has an expression based default value. I would
think either you can have an expression as a default value, or you can't -
the ability to assign the default through the designer makes it appear that
that is ok, while later fiddling through RS makes it seem like it is wrong -
do you think possibly it's a bug?
Thanks,
Pete
"David Siebert" wrote:
> The reason you aren't seeing any value in the Default Value box is because
> your default value is an expression. The Default Value textbox on the
> Parameters property page only displays default values when they are strings
> and not expressions (this does not mean that you do not have a default value
> when it is an expression). The reason you might be getting an error is if
> your parameter type is date, you're returning a string instead of a date. I
> don't know what your parameter type is, but it is just a thought. Hope that
> helps you a bit.
> David
> "Myles" wrote:
> > I think you can try setting the default value in VS (designer) as
> >
> > ="Yes" instead of Yes
> >
> > see if that works.
> >
> > That being said, I am having some difficulty because it appears setting
> > things in the designer (for parameters) and setting parameter properties on
> > RS behaves in different ways. The prompt user, prompt string, default value
> > etc. seems to not be communicating clearly with what was set in the
> > designer. Example - if you have a date parameter, and in the designer you
> > set the default to be =Left(today, 10) - an expression, in other words - when
> > you go to look in RS and tweak the parameter properties it has default value
> > checked, but it does not sjow the expression and it doesn't see any valid
> > default value - and gives an error.
> >
> >
> > "anandr" wrote:
> >
> > > I have a report which takes few parameters. I have set some defalut value for
> > > them. The default values work good when i Preview teh report. But when i
> > > deploy the report to the Report Server, the default values get lost and the
> > > user has to type them all again. Any clue on how to solve this issue?|||I've noticed this also. I've gotten around it by unchecking the Has Default
boxes for any parameters that have a calculated value. The calculated
default values will still be there after you apply changes, and if you go
back to the properties page, you should see that the Has Default boxes are
checked again. I don't know if I would really consider this a major bug, but
a bug it may be. You can definitely use expressions as default values, but I
will caution you that using them can cause odd behavior when editing the
default values when actually running the report. If you have defaults that
are expressions and you change a parameter value, it will recalculate any
calculated default values for all the parameters after the one changed. This
is in order to allow cascading parameters, and can't really be changed as far
as I know. I actually use calculated values a lot (for dates e.g. beginning
of month, end of month, two weeks ago, etc.) but in order to get around the
odd behavior of cascading parameters, I will use sql to get the default
dates, and then set the default in VS to "From Query" and this manages to
work around the recalculation issue.
Hope this helps.
David
"Myles" wrote:
> Thanks David -
> actually, the parm type is a string - I believe that is the only way
> something like
> =Left(today, 10) would work, because it is a string function (basically).
> It is trying, though, when you open up the parameters page of the properties
> tab on http://<Server>/Reports and fiddle with a completely different
> parameter and try to apply the changes, that it gives you the error on any
> string type parameter that has an expression based default value. I would
> think either you can have an expression as a default value, or you can't -
> the ability to assign the default through the designer makes it appear that
> that is ok, while later fiddling through RS makes it seem like it is wrong -
> do you think possibly it's a bug?
> Thanks,
> Pete
>
> "David Siebert" wrote:
> > The reason you aren't seeing any value in the Default Value box is because
> > your default value is an expression. The Default Value textbox on the
> > Parameters property page only displays default values when they are strings
> > and not expressions (this does not mean that you do not have a default value
> > when it is an expression). The reason you might be getting an error is if
> > your parameter type is date, you're returning a string instead of a date. I
> > don't know what your parameter type is, but it is just a thought. Hope that
> > helps you a bit.
> >
> > David
> >
> > "Myles" wrote:
> >
> > > I think you can try setting the default value in VS (designer) as
> > >
> > > ="Yes" instead of Yes
> > >
> > > see if that works.
> > >
> > > That being said, I am having some difficulty because it appears setting
> > > things in the designer (for parameters) and setting parameter properties on
> > > RS behaves in different ways. The prompt user, prompt string, default value
> > > etc. seems to not be communicating clearly with what was set in the
> > > designer. Example - if you have a date parameter, and in the designer you
> > > set the default to be =Left(today, 10) - an expression, in other words - when
> > > you go to look in RS and tweak the parameter properties it has default value
> > > checked, but it does not sjow the expression and it doesn't see any valid
> > > default value - and gives an error.
> > >
> > >
> > > "anandr" wrote:
> > >
> > > > I have a report which takes few parameters. I have set some defalut value for
> > > > them. The default values work good when i Preview teh report. But when i
> > > > deploy the report to the Report Server, the default values get lost and the
> > > > user has to type them all again. Any clue on how to solve this issue?|||Excellent David - thank you! Yes I noticed if you un-check the 'has default
value' check box, the problem does go away and you retain the expression
based value. This is good to know! Thanks!
Pete
"David Siebert" wrote:
> I've noticed this also. I've gotten around it by unchecking the Has Default
> boxes for any parameters that have a calculated value. The calculated
> default values will still be there after you apply changes, and if you go
> back to the properties page, you should see that the Has Default boxes are
> checked again. I don't know if I would really consider this a major bug, but
> a bug it may be. You can definitely use expressions as default values, but I
> will caution you that using them can cause odd behavior when editing the
> default values when actually running the report. If you have defaults that
> are expressions and you change a parameter value, it will recalculate any
> calculated default values for all the parameters after the one changed. This
> is in order to allow cascading parameters, and can't really be changed as far
> as I know. I actually use calculated values a lot (for dates e.g. beginning
> of month, end of month, two weeks ago, etc.) but in order to get around the
> odd behavior of cascading parameters, I will use sql to get the default
> dates, and then set the default in VS to "From Query" and this manages to
> work around the recalculation issue.
> Hope this helps.
> David
> "Myles" wrote:
> > Thanks David -
> >
> > actually, the parm type is a string - I believe that is the only way
> > something like
> > =Left(today, 10) would work, because it is a string function (basically).
> > It is trying, though, when you open up the parameters page of the properties
> > tab on http://<Server>/Reports and fiddle with a completely different
> > parameter and try to apply the changes, that it gives you the error on any
> > string type parameter that has an expression based default value. I would
> > think either you can have an expression as a default value, or you can't -
> > the ability to assign the default through the designer makes it appear that
> > that is ok, while later fiddling through RS makes it seem like it is wrong -
> > do you think possibly it's a bug?
> >
> > Thanks,
> >
> > Pete
> >
> >
> >
> > "David Siebert" wrote:
> >
> > > The reason you aren't seeing any value in the Default Value box is because
> > > your default value is an expression. The Default Value textbox on the
> > > Parameters property page only displays default values when they are strings
> > > and not expressions (this does not mean that you do not have a default value
> > > when it is an expression). The reason you might be getting an error is if
> > > your parameter type is date, you're returning a string instead of a date. I
> > > don't know what your parameter type is, but it is just a thought. Hope that
> > > helps you a bit.
> > >
> > > David
> > >
> > > "Myles" wrote:
> > >
> > > > I think you can try setting the default value in VS (designer) as
> > > >
> > > > ="Yes" instead of Yes
> > > >
> > > > see if that works.
> > > >
> > > > That being said, I am having some difficulty because it appears setting
> > > > things in the designer (for parameters) and setting parameter properties on
> > > > RS behaves in different ways. The prompt user, prompt string, default value
> > > > etc. seems to not be communicating clearly with what was set in the
> > > > designer. Example - if you have a date parameter, and in the designer you
> > > > set the default to be =Left(today, 10) - an expression, in other words - when
> > > > you go to look in RS and tweak the parameter properties it has default value
> > > > checked, but it does not sjow the expression and it doesn't see any valid
> > > > default value - and gives an error.
> > > >
> > > >
> > > > "anandr" wrote:
> > > >
> > > > > I have a report which takes few parameters. I have set some defalut value for
> > > > > them. The default values work good when i Preview teh report. But when i
> > > > > deploy the report to the Report Server, the default values get lost and the
> > > > > user has to type them all again. Any clue on how to solve this issue?|||Where is the "Has Default" checkbox? I could not locate it in "Report
Parameters" screen
"David Siebert" wrote:
> I've noticed this also. I've gotten around it by unchecking the Has Default
> boxes for any parameters that have a calculated value. The calculated
> default values will still be there after you apply changes, and if you go
> back to the properties page, you should see that the Has Default boxes are
> checked again. I don't know if I would really consider this a major bug, but
> a bug it may be. You can definitely use expressions as default values, but I
> will caution you that using them can cause odd behavior when editing the
> default values when actually running the report. If you have defaults that
> are expressions and you change a parameter value, it will recalculate any
> calculated default values for all the parameters after the one changed. This
> is in order to allow cascading parameters, and can't really be changed as far
> as I know. I actually use calculated values a lot (for dates e.g. beginning
> of month, end of month, two weeks ago, etc.) but in order to get around the
> odd behavior of cascading parameters, I will use sql to get the default
> dates, and then set the default in VS to "From Query" and this manages to
> work around the recalculation issue.
> Hope this helps.
> David
> "Myles" wrote:
> > Thanks David -
> >
> > actually, the parm type is a string - I believe that is the only way
> > something like
> > =Left(today, 10) would work, because it is a string function (basically).
> > It is trying, though, when you open up the parameters page of the properties
> > tab on http://<Server>/Reports and fiddle with a completely different
> > parameter and try to apply the changes, that it gives you the error on any
> > string type parameter that has an expression based default value. I would
> > think either you can have an expression as a default value, or you can't -
> > the ability to assign the default through the designer makes it appear that
> > that is ok, while later fiddling through RS makes it seem like it is wrong -
> > do you think possibly it's a bug?
> >
> > Thanks,
> >
> > Pete
> >
> >
> >
> > "David Siebert" wrote:
> >
> > > The reason you aren't seeing any value in the Default Value box is because
> > > your default value is an expression. The Default Value textbox on the
> > > Parameters property page only displays default values when they are strings
> > > and not expressions (this does not mean that you do not have a default value
> > > when it is an expression). The reason you might be getting an error is if
> > > your parameter type is date, you're returning a string instead of a date. I
> > > don't know what your parameter type is, but it is just a thought. Hope that
> > > helps you a bit.
> > >
> > > David
> > >
> > > "Myles" wrote:
> > >
> > > > I think you can try setting the default value in VS (designer) as
> > > >
> > > > ="Yes" instead of Yes
> > > >
> > > > see if that works.
> > > >
> > > > That being said, I am having some difficulty because it appears setting
> > > > things in the designer (for parameters) and setting parameter properties on
> > > > RS behaves in different ways. The prompt user, prompt string, default value
> > > > etc. seems to not be communicating clearly with what was set in the
> > > > designer. Example - if you have a date parameter, and in the designer you
> > > > set the default to be =Left(today, 10) - an expression, in other words - when
> > > > you go to look in RS and tweak the parameter properties it has default value
> > > > checked, but it does not sjow the expression and it doesn't see any valid
> > > > default value - and gives an error.
> > > >
> > > >
> > > > "anandr" wrote:
> > > >
> > > > > I have a report which takes few parameters. I have set some defalut value for
> > > > > them. The default values work good when i Preview teh report. But when i
> > > > > deploy the report to the Report Server, the default values get lost and the
> > > > > user has to type them all again. Any clue on how to solve this issue?|||I have run into the same issue.
I have defined 6 possible values for a parameter in a report. They are team
names - so they would look like:
Team 1
Team 2
and so on... I have defined Team 1 as the default selection in each report.
(by setting the default, unqueried value to: Team 1. If I use ="Team 1" or
something like that then it errors. And this appears to work correctly when
using the vs dev env. However when the report is published the selection
for team does not default to Team 1, it defaults to <Select A Value>.
Any ideas?
Thanks.
--Cory
"anandr" wrote:
> I have a report which takes few parameters. I have set some defalut value for
> them. The default values work good when i Preview teh report. But when i
> deploy the report to the Report Server, the default values get lost and the
> user has to type them all again. Any clue on how to solve this issue?

Default values for datetime parameters

Hi all,

I have a report that needs a to-date and a from-date as input. I would like them to be set to today by default.

I have set the data type for both parameters to DateTime and the default value as "Non-queried" = Today()

This does fill in the dates with today, but I cannot change the value in the fields, until the report has been generated once. I just want the date to be equal to today since 90% of the time that is what my users wants to see - but I want to give the last 10% the chance to change the date without having to generate the report first.

The date-fields are locked until some of the other parameters are filled in... It makes no sense really.

Hope you can help me here :-D

-- Heidi, Denmark

I have the following report parameters set that generate default From & To dates as the previous months 1st & Last Day. Both Available Parameters & Default Parameters are set to "Non-Queried"

The third parameter (groupid) defaults to a Null value but user can choose from a list of valid values.

When I deploy this report, the user can change the From & To dates without first running the report.

I'll attach the parameters XML

<ReportParameters>

<ReportParameter Name="startdate">

<DataType>DateTime</DataType>

<DefaultValue>

<Values>

<Value>=dateadd("m",-1,dateadd("d",-day(today)+1,today))</Value>

</Values>

</DefaultValue>

<Prompt>Select From Date</Prompt>

</ReportParameter>

<ReportParameter Name="enddate">

<DataType>DateTime</DataType>

<DefaultValue>

<Values>

<Value>=dateadd("d",-day(today),today)</Value>

</Values>

</DefaultValue>

<Prompt>Select To Date</Prompt>

</ReportParameter>

<ReportParameter Name="groupid">

<DataType>String</DataType>

<Prompt>Select Hierarchy Group</Prompt>

<ValidValues>

<DataSetReference>

<DataSetName>H_Groups</DataSetName>

<ValueField>id</ValueField>

<LabelField>List</LabelField>

</DataSetReference>

</ValidValues>

</ReportParameter>

</ReportParameters>

Does this help at all?

|||

Hi,

I've tried setting the dates like you do, but that doesn't help me. The user still isn't able to change the date values.

I have 6 parameters:

"Product" e.g. Ham (character)

"Batch" e.g. 121434 (character)

"From date" (datetime)

"From time" 05:00 (character)

"To date" e.g. (datetime)

"To time" e.g. 11:30 (character)

I only have default values for the date fields. The user cannot change the date values until he has entered something in the other parameters. It is like the date fields are disabled somehow and the default date isn't even displayed to the user (the field is simply grey...)

I suspect that it is because I use built-in functions instead of data from a query (I've tried making an sql selecting today, but I cannot really get that to work - problems with the formatting) :-S

|||

Heidi Christiansen wrote:

I suspect that it is because I use built-in functions instead of data from a query (I've tried making an sql selecting today, but I cannot really get that to work - problems with the formatting) :-S

I'm using built-in functions as well, so I don't think that's it.

Try making your date parameters the first ones to be chosen. I think this fixes it for you, although I don't really understand why this should be the case. I suspect it would be "by design"

|||

LOL

That helped... strange design decisions....

Thank you for your help :-D

Default Values does not include all the values (Cascading Parameters)

A have a multi-valued parameter (B) which is dependent on a single-valued parameter (A) on my report. When a value is selected in A, I want all matching values in B to be selected by default and the "Select All" option checked. To do this I have set the Default Values section in B to point to the same dataset as the "Available Values" section. Both A and B have default values so the report runs automatically.

One of the values in parameter A (say Value1) yields more values in parameter B than the other (say Value2).

If I run the report the first time with Value1 selected as the default for parameter A, all values in B are checked correctly. If I run the report with Value2 selected the first time and then change the selected value to Value2 and run my report, all values in B are displayed but only the values that were previously checked (when Value1 was selected), are now checked, leaving the "Select All" unchecked.

What am I doing wrong? Why are all the values in B not checked? The dataset is the same in "Available Values" section and "Default Values" section.

Anyone?|||

I am having the same issue and am unable to fix. My parent parameter is also a multi select. The only way the child values that are selected by default change is when the parent parameter used before the changed is no longer selected. I still haven't discovered a solution.

|||

I am running RS2005, SP2. I have the same problem with slightly different scenario. I have two multi-value parameters, parameter B depends on parameter A. A contains value x, y z. When value x is selected in parameter A, parameter B is refreshed with a matching list where all values selected. However, when I add y to the selection for parameter A, parameter B refreshed with a matching list for both x and y, but only those values associated with x are selected.

Is this a bug? If not how can I do to fix the problem?

Thanks.

SouBee

|||I now have a scenario same as SouBee's with the same result. Can someone tell me if there is a way to fix this?|||

I just found out that this was reported in January 07 and supposedly fixed in SP2. I am running SQL Server 2005 Standard edition SP2. I still have this issue. Was this fixed in Enterprise edition only? When will this be fixed in standard edition?

http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=249637

|||I have enterprise and developer. Same issues. Doens't seem like it fixed it.|||https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=268032|||Perhaps you can send them that feedback