Parameter Does Not Exist in Parameters Collection

• cdun2

  SSCertifiable

  Points: 7893

  More actions

  November 15, 2012 at 1:42 pm

  #271022

  In my report, I have a parameter that returns a list of agencies based on a cross reference to user accounts. I want to leverage the Sharepoint CurrentUser filter so that when a user views the report, they only see applicable agencies in the parameter list.

  In my report, the query that returns the data to the report requires an @AgencySummary query parameter. The WHERE clause calls a table function named dbo.CorporateHierarchy(@Hvalue) to return one or more agencies:

  SELECT MTD_Actual FROM dbo.ReportData WHERE Agency IN (select HValue from dbo.CorporateHierarchy(@AgencySummaryLocal))

  I have a report parameter named @Agency. The report parameter @Agency is configured to the @AgencySummary query parameter in the dataset that returns the data.

  The @Agency report parameter gets its Available Values from another dataset named DS_AgencyListBySecurityAccount. This dataset has a parameter called @SecurityAccountName. The intent with this one is to return a list of agencies based on a match to a user account. For this purpose, I have created a report parameter named @SharePointAccount. It is not configured with Available Values nor a Default Value. It is configured to the @SecurityAccountName query parameter of the DS_AgencyListBySecurityAccount dataset.

  With the report deployed to Sharepoint, I want to configure the @SharePointAccount report parameter to the CurrentUserFilter. The user account would then ultimately drive the list of Agencies returned.

  In VS BIDS 2008 R2, when I attempt to preview the report (and this also happens from the Sharepoint Report Viewer), I get the following message:

  An error has occurred during report processing. (rsProcessingAborted)

  The Value expression for the query parameter ‘@SecurityAccountName’ contains an error: The expression that references the parameter 'SharePointAccount' does not exist in the Parameters collection. Letters in the names of parameters must use the correct case. (rsRuntimeErrorInExpression)

  I can't figure out why I'm getting this error. Why does the @SharePointAccount report parameter 'not exist in the Parameters collection'? I did some research on this at this site, but I didn't find much that addressed this error.

  Thank you for your help.

  CSDunn

• cdun2

  SSCertifiable

  Points: 7893

  More actions

  November 18, 2012 at 6:43 am

  #1560084

  This turned out to be an issue with the way I was cascading my parameters. I had the parameters in the wrong 'physical' order.

  CSDunn