Monday, January 6, 2014

ParameterName is not a parameter in stored procedure StoredProcName in econnect

I updated the parameter list in a stored proc, let's called it DoStuff, then was getting an error "This @ParameterName is not a parameter in the stored proc DoStuff"

I had to restart the eConnect service before it would start working with the updated param list. Apparently eConnect caches param lists for stored procs? I guess that's OK if you assume your stored procs are rarely going to change. Since I'm doing development with a ton of customizations this is rather a pain in the ass. I'm glad I discovered this early.

No comments:

Post a Comment