February 1, 2012 at 6:42 pm
Hello All,
Seems like a bug but I'm probably doing something wrong.
I have a parameter (@NorthSouth) which has two options, North or South. I am specifying the values and I am setting a default value of 'North'.
I have a second parameter (@Accounts) which should show account data based on the selection in the @NorthSouth parameter.
The available values for the second parameter are based on a stored procedure. The procedure looks something like this
CREATE PROCEDURE uspAccounts
@NorthSouth char (5)
AS
SELECT * FROM Accounts
WHERE AccountRegion = @NorthSouth
When I load the report with the default value of 'North' I see the proper accounts. When I switch to South the parameters updates, the screen redraws, but the Accounts drop-down is empty. If I switch back to "north' it works.
I ran profiler when changing the @NorthSouth parameter and the procedure is being called properly. I can return data with both profiler statement. But the Accounts dropdown never shows account when I select 'south' only when I select 'north'.
If I change the default of @NorthSouth to 'south' no data is returned. If I then switch the parameter to 'north' in the dropdown then data is returned.
Please help if you can....
February 3, 2012 at 12:29 pm
Operator error, product is working as designed.
In my proc there were two select statements embedded in if clauses. The fields were not aliased consistently in the two select statements.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply