You are viewing limited content. For full access, please sign in.

Question

Question

Workflow Custom Query - Error converting datatype nvarchar to date [Wf 9.1.0.328]

asked on February 9, 2015 Show version history

This is the first time I'm trying to use Workflow Custom Query to EXECUTE a SQL Stored Procedure.  I am able to EXECUTE the SP using SSMS, but unable to successfully test using Workflow.  When I click on test and manually populate data for the parameters, I get a conversion error (pasted below)

Will someone point me in the right direction?

0 0

Answer

SELECTED ANSWER
replied on February 9, 2015 Show version history

Never mind.... Figured it out.  It just doesn't feel right using the same Parameter Name of '?' for different Parameter Values

http://www.laserfiche.com/support/webhelp/workflow/9.1/en-US/lfworkflow.htm#Resources/Activities/Custom Query.htm?Highlight=custom query 

3 0
replied on December 8, 2016

Thanks for the help on this Eddie.  I was facing the same problem.  I don't like using '?' for parameters either.  I'd like to ask Laserfiche for an enhancement request to fix this up to be able to use named parameters in "Parameter Names" when executing stored procedures.  Relying on parameter order is a bad practice.

Thanks.

0 0
replied on December 8, 2016

This is a limitation in the ODBC standard, not a Laserfiche design choice. You can switch to OLE drivers, those allow for named parameters.

1 0
replied on December 8, 2016

Thanks for the response Miruna.  When I created my data source in Workflow I chose "Direct connections".

By using this method the connection shows up as ODBC.

How do I set up an OLE connection?  Do I need to use the "Expert (Connection strings)" option?

The documentation mentions OLE as a choice but it does not show up for me.  I am using Workflow 10.0.0.249

 

 

replied on December 8, 2016

Thanks so much Miruna.  I changed my data connection and was able to use named parameters.

I think the documentation in this area could use a bit of enhancement.

0 0
replied on December 8, 2016

Will look into it, thanks for pointing that out.

0 0

Replies

You are not allowed to reply in this post.
You are not allowed to follow up in this post.

Sign in to reply to this post.