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

Question

Question

SQL Data Type Uniqueidentifier

Workflow Version 10
Updated March 4, 2018
asked on March 1, 2018

Can anyone tell me if the SQL type of Uniqueidentifier was really fixed in V10.  I am on 10.2 and having the same issue.  The fields with a data type of uniqueidentifier are not available to me in query results.

 

https://answers.laserfiche.com/questions/51272/The-SQL-column-type-is-not-supported-in-LFQL#86407

 

0 0

Answer

SELECTED ANSWER
replied on March 2, 2018

I think i see what you mean. I set up a Query Data that retrieves values from a uniqueidentifier column in a SQL table. When I run over  the results with For Each Value and track tokens, the value was retrived correctly. However, if i try to use the current value in another activity, the token is not there in the tokens menu:

Does that sound like what you're seeing?

If I open the token dialog, the token is listed.

When I picked it from that list while setting up a second Query Data activity, the editbox underlined it as invalid. I clicked OK and ignored the underlining and it works fine at runtime.  Other activities don't seem to have this same issue.

So it looks to me like it's a UI bug at this point, but the token is available and the value is passed around correctly when the workflow runs.

0 0

Replies

replied on March 1, 2018

The thread you linked is a Laserfiche Server issue with dynamic template fields. That bug has been fixed and it looks to be working fine in 10.2.

Your thread is tagged as Workflow, so are you talking about something else? Query data seems to get the values correctly from a uniqueidentifier column in Workflow 10.2.

0 0
replied on March 1, 2018

I must have misread the link.  I am talking about doing SQL queries in Workflow.  I use 10.2.0.216 and when doing a query to a SQL database, any field that is data type uniqueidentifier is not available to me after the query is run.

What I am trying to do is run a query on a table that finds all records.  Use those results and use 1 field (the uniqueidentifier fields) to find matching records in a different table.

0 0
SELECTED ANSWER
replied on March 2, 2018

I think i see what you mean. I set up a Query Data that retrieves values from a uniqueidentifier column in a SQL table. When I run over  the results with For Each Value and track tokens, the value was retrived correctly. However, if i try to use the current value in another activity, the token is not there in the tokens menu:

Does that sound like what you're seeing?

If I open the token dialog, the token is listed.

When I picked it from that list while setting up a second Query Data activity, the editbox underlined it as invalid. I clicked OK and ignored the underlining and it works fine at runtime.  Other activities don't seem to have this same issue.

So it looks to me like it's a UI bug at this point, but the token is available and the value is passed around correctly when the workflow runs.

0 0
replied on March 4, 2018

That is exactly what I am talking about.  I will try it through the token dialog.

 

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

Sign in to reply to this post.

Details
Related Posts
Loading ...