Report Parameter has DefaultValue or ValidValue.....Forward Dependencies are not valid

• clay-260236

  SSC Veteran

  Points: 296

  More actions

  September 13, 2005 at 9:36 pm

  #110003

  Can anybody tell me what I'm doing wrong here:

  I get this error message in some form or another no matter what:

  The report parameter ‘Campaign’ has a DefaultValue or a ValidValue that depends on the report parameter "Campaign". Forward dependencies are not valid.

  I've studied 3 books, 3 online tutorials and can make the parameters work every time.  For my real life scenario, it just won't work.

  I have 2 datasets and am obviously trying to give the user the option to choose which campaign they want to view.

  #1:  dsTelco:

  SELECT  CallType, DisTime - AnswerTime AS ConnectTime

  FROM dbo.CTK 

   WHERE TCD IN('AM','HU','NM','VC','NT')

   OR AgentID LIKE '[a-z,0-9]%'

   ORDER BY CallDate

  #2:  dsCampaign

  SELECT P.CampaignID, P.CampDesc, C.Campaign

  From dbo.CPro P, dbo.CTK C

  WHERE (P.CampaignID = C.Campaign)

  AND (P.CampDesc = @Campaign)

  I set the the report parameters as follows:

  Paramater: Campaign

  datatype: Sting

  Available Values: Non-Queried

  Default Values: From Query >>Dataset: dsCampaign >> ValueField: Campaign

  I've spun my wheels for at least 10 hours and still can't get it to work out after many different iterations.  The only way I can get this parameter to work is if I place static campaign names in the Available values selection.  Can anybody offer some helpful guidance on this?  I'm about out of ideas!!

  Thanks,

  Clay

• clay-260236

  SSC Veteran

  Points: 296

  More actions

  September 14, 2005 at 11:43 pm

  #590009

  Thanks folks.........I figured it out...

   

  Clay

• Benjamin Lieb

  Valued Member

  Points: 55

  More actions

  November 8, 2005 at 2:21 pm

  #602892

  so what was it?

• lcarrethers

  SSCommitted

  Points: 1917

  More actions

  June 14, 2011 at 10:51 am

  #1338543

  How did you get this to work. I having the same problem

• Daniel Bowlin

  SSC-Dedicated

  Points: 34566

  More actions

  June 14, 2011 at 11:00 am

  #1338547

  Change the order of parameters so that your dependant parameter is below the parameter that feeds it.

• lcarrethers

  SSCommitted

  Points: 1917

  More actions

  June 14, 2011 at 11:02 am

  #1338552

  I did. Here is the simple code i have

  select * from fleetsize where [plant code] in (@plantcode) and order_date between @startdate and @enddate

• Daniel Bowlin

  SSC-Dedicated

  Points: 34566

  More actions

  June 14, 2011 at 12:57 pm

  #1338621

  Please post your error.

• lcarrethers

  SSCommitted

  Points: 1917

  More actions

  June 14, 2011 at 1:35 pm

  #1338630

  I got it to work.

  I had to add @plantcode variable to the end of my first dataset

  select * from fleetsize where order_date between @startdate and @enddate and [plant code] in (@plantcode)

  and here is the dataset of the second one

  select distinct [plant code] from fleetsize where order_date between @startdate and @enddate

  and my @plantcode report properties are set up like this:

  Available values = from query

  dataset = Fleetsize2 (which is the 2nd data)

  Value field = plant_code (This is the filed the paramter chooses from)

  label field = plant_code (This is the filed the paramter chooses from)

  I left Default values = null