SSRS multiple values parameter not working

I have a report showing Sales Order information, basically a Header section and a Sub-report showing the lines. The report has a parameter defined for the order number. Everything works great when showing a single order.

However, if select more than 1 order in the parameter drop-down, then the report is blank.
I'm using 3 data sets: Header Detail, Line Detail & a 3rd for the Order Number query.

The parameter value(s) for the header and lines datasets are set to use the values returned from this 3rd dataset.

This piece is working as I do get a correct list of Order Numbers to select in the drop-down, it just won't work if I choose more than 1 (or All).

What am I missing??
BrianFordAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Jim HornMicrosoft SQL Server Developer, Architect, and AuthorCommented:
I don't have an immediate answer for you, but SQL expert and MVP Valentino Vranken has an article out on Reporting On Data From Stored Procedures (part 2), where the top section is Creating A Multi-Value Report Parameter.

Good luck.
Jim
0
BrianFordAuthor Commented:
Thanks,

I'm not using a stored Procedure but my report is setup just like this in that it uses the same method of joining the parameter, i.e.

 (=Join(Parameters!DepartmentList.Label, ", ")"

but it just doesn't show multiple records :(
0
Koen Van WielinkBusiness Intelligence SpecialistCommented:
Hi Brian,

Are you using a split function to separate your parameter in separate values? When using a multi value parameter SSRS passes this as a string value to the dataset. You have to split them before they can be used in an "IN" statement.
0
The 7 Worst Nightmares of a Sysadmin

Fear not! To defend your business’ IT systems we’re going to shine a light on the seven most sinister terrors that haunt sysadmins. That way you can be sure there’s nothing in your stack waiting to go bump in the night.

ValentinoVBI ConsultantCommented:
If you're not using a stored proc then you don't need to use Join() to pass the multi-valued parameter into the dataset.  Just specify your parameter as if it were single-valued: Parameters!OrderNumber.Value

And use IN() in the WHERE clause: WHERE YourOrderNumberField IN ( @OrderNumber )
0
ValentinoVBI ConsultantCommented:
Koen: the join/split is only needed when using stored procs.  If the query code resides in the dataset then somehow SSRS knows how to deal with the array of values.
0
Koen Van WielinkBusiness Intelligence SpecialistCommented:
Ah, ok. Thanks for that piece of info Valentino. I've only ever worked with procedures and assumed it was always required.
My apologies Brian.
0
BrianFordAuthor Commented:
Thanks guys.  I'll check this out later today and let you know how I get on
0
BrianFordAuthor Commented:
OK, getting closer :)

The report now runs and show information, however it shows ALL the lines for ALL the orders against just the one order header.

Here's what I have:
A Parameter called OrderNumber
An OrderNumber dataset (a query which returns a list of order numbers) that the above parameter uses
A header dataset -  which uses the above parameter (=Parameters!OrderNumber.Value)
A Lines Dataset - which again uses the above parameter (=Parameters!OrderNumber.Value)

Pretty sure I'm missing something that splits the report by header record?
0
Koen Van WielinkBusiness Intelligence SpecialistCommented:
Sounds like there's something amiss in your SQL query, but hard to tell without actually seeing it.
Also, is there a particular reason you have separate datasets for the headers and lines? Can't you use a single dataset and use groups to separate the two? This would prevent your report from having to run over your orders twice, most likely improving performance.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
BrianFordAuthor Commented:
thanks
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft IIS Web Server

From novice to tech pro — start learning today.