September 6, 2006 at 7:27 am
I am working on reports from our HR system that allow a manager to only see their own direct reports data. This works fine by using the global UserID field parameter and joining to a table that contains the employee id of the supervisor as well as their network signon and then finding all the records in the personal data table where the supervisor id matches the value in this table.
However, some reports should be run on an individual and not all employees. My thought was to create a dataset where I look up all the employee ids and names that report to a supervisor as above. Then I would use this list to populate a dropdown list that the supervisor could use to choose an employee and then pass that parameter to the dataset that would populate the report. Seems logical to me but I get the following error
[rsInvalidReportParameterDependency] The report parameter ‘Emplid’ has a DefaultValue or a ValidValue that depends on the report parameter “SupSignon”. Forward dependencies are not valid.
Build complete -- 1 errors, 0 warnings
If a parameter can not depend on another parameter I need some help to think outside this box I have created for myself as to how to accomplish this task.
September 6, 2006 at 6:04 pm
It sounds to me like the order of the parameters are wrong. Does the SupID parameter appear above the EmpId parameter in the Visual Studio Parameter box?
Just a stab, but I've had that issue before.
______________________________________________________________________
Personal Motto: Why push the envelope when you can just open it?
If you follow the direction given HERE[/url] you'll likely increase the number and quality of responses you get to your question.
Jason L. SelburgSeptember 7, 2006 at 6:42 am
That was exactly it. I didn't realize the order they appeared in the list was important. I do now. Thank you.
April 2, 2007 at 3:39 pm
Thanks Jason!
That's just what I needed too!
November 28, 2007 at 4:00 pm
thanks Jason.. i was banging my head before i read your reply...
January 31, 2008 at 7:54 am
hi,
i also had the same issue..
thanks for your reply.. now i could rectify it..
but now another issue i have..
i am using one dataset to populate a dropdown list which selecteditem is the input to second dataset..
and i have 3rd dataset which is dependant on 2nd dataset selected parameter..
if i select a particular item from the 1st dataset(dropdown list), i will not populate the 2nd dropdownlist(no o/p from 2nd dataset) .. but the 3rd data set does not require the 2nd dataset o/p to actually produce the output ie, that field can be null...
but this feature iam not able to implement ..
pls help ...
Thanks in advans........
January 31, 2008 at 7:58 am
If I understand you correctly, add a "dummy" parameter to the dataset that you're using for #2 that will come up if that particular parameter from #1 is selected.
______________________________________________________________________
Personal Motto: Why push the envelope when you can just open it?
If you follow the direction given HERE[/url] you'll likely increase the number and quality of responses you get to your question.
Jason L. SelburgFebruary 7, 2008 at 9:11 pm
Thanks for ur reply.. it worked.. but another issue came..
In my report i have 8 parameters.. and 3 are passed from code (from codebehind), and the rest 5 parameters will accept input from user.. but these 5 parameters depends on the role of the logged in user.. depending on the role 3- 4 parameter will get values from the user input.. the remaing 1-2 parameters will be passed with default(dummy) vaues. these are multi valued parameters...
but while running the report i am geting error " ABC" Parameter missing a value ..
Thanks in advance .........
Pls help...
March 13, 2008 at 5:33 pm
Good morning All,
Changing the order of the parameters worked a treat for me. Very _very_ happy with that. I thought I might have to throw this whole report in the bin when I saw that error... T.T
Cheers - Damien
April 10, 2008 at 7:05 am
Result!
Thanks very much!
May 1, 2008 at 2:58 pm
Thanks
January 31, 2009 at 9:40 am
changing order from Report Parameters... did not work for me. any thoughts?
February 25, 2009 at 5:53 pm
I was modifying a report that needed to behave just like yours when I ran into this error. I switched the order of the parameters and everything worked correctly. Thank you very much for this tip.
August 21, 2009 at 2:50 pm
Hello
I am having the exact same issuse and changing the order is not helping me...
Summary of the problem:
SELECT a,b,c,, getdate() -90 AS defaultstartdate, getdate()-60 AS defaultenddate
FROM x,y,z
WHERE x.date BETWEEN @startdate AND @enddate
@startdate and @enddate are setup as date/time with defualt values of defaultstartdate and defaultenddate respectively....
I am getting the "Forward dependencies are not valid." errors...
PLEASE HELP!!!
Thanks
MAX
August 23, 2009 at 5:32 pm
defaultstartdate and defaultenddate need to be calculated in a separate data set from your report data set. What you have defined in your query is that the parameters you want to filter the result set on are dependant on what the result set returns. See the circle there?
Viewing 15 posts - 1 through 15 (of 36 total)
You must be logged in to reply to this topic. Login to reply