error: non-existing report parameter

Question

Post reply

error: non-existing report parameter

kcha2004

Right there with Babe

Points: 773
More actions
September 21, 2015 at 4:05 pm

#320730

Hello Everyone,
I get this error: "The value expression for the query parameter '@eDate' refers to a non-existing report parameter 'eDate'. Letters in the name of the parameters must use the correct case."
I use lower case in all of my queries. The parameter my queries reference is @edate. To find @eDate, I copied every query to text doc and looked for the word eDate and didn't fine any. Why does it still reference eDate? What am I missing?
Thank you very much for any input.

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply

pietlinden SSC Guru Points: 63503 More actions · Answer 1

Check the server collation value. It could be case-sensitive.

http://blog.sqlauthority.com/2007/04/30/case-sensitive-sql-query-search/

http://stackoverflow.com/questions/14270993/case-sensitive-variable-names-in-sql-server

Spiff SSCertifiable Points: 7826 More actions · Answer 2

I've run into a similar issue before. Did you rename that parameter in SSRS at any point? I've found SSRS doesn't always update the new name everywhere.

Right click the dataset ang open properties then go to Parameters. You'll see parameter name and value. While it may look correct, click on the expression button next to the parameter value and look at the expression within. If it's in the incorrect case e.g. =Parameters!eDate.Value you need to correct it here.

kcha2004 Right there with Babe Points: 773 More actions · Answer 3

Thank you everyone for your help! I found the error in one of the expressions. Thank you!:-)

Jack 95169 SSC-Addicted Points: 410 More actions · Answer 4

Thanks Spiff - I had indeed renamed the field, and SSRS hadn't picked it up

jonathan.crawford SSCertifiable Points: 6612 More actions · Answer 5

old thread, but I'll add my two cents. I have also corrected by opening the xml and fixing it in Notepad++ or similar, works fine that way too.

-------------------------------------------------------------------------------------------------------------------------------------
Please follow Best Practices For Posting On Forums to receive quicker and higher quality responses

rgouette SSC Journeyman Points: 82 More actions · Answer 6

Spiff wrote:

....click on the expression button next to the parameter value and look at the expression within. If it's in the incorrect case e.g. =Parameters!eDate.Value you need to correct it here.

still being used in 2020 to fix the same issue..

I blame COVID!!

thanks mate.. 🙂