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

Question

Question

double quote in path throws off Workflow search

asked on May 23, 2014 Show version history

 I found this thread on this topic, but was not sure if this functionality was added to Workflow:

 

https://answers.laserfiche.com/questions/52030/Feature-Request-Function-to-convert-token-from-string-with-quotes-to-double-quotes-for-searches

 

In workflow, I have a query that pulls data that has a single " in a field. That field is later used in a search where the " appears in a path that is being searched. 

 

After looking at this in client, I see that an extra " is added in  automatically. In the client:

 

Palm-Beach\Purchasing\REQs POs COs\FY14\PO__SPRAY HEAD, POP-UP, 4" -

2/27/2014__140926\369-13-07F

 

becomes

 

Palm-Beach\Purchasing\REQs POs COs\FY14\PO__SPRAY HEAD, POP-UP, 4"" - 2/27/2014__140926\369-13-07F

 

Not so in workflow, and it is throwing off my search. Is there a hotfix out there that addresses this issue?

 

Thank you in advance.

0 0

Answer

SELECTED ANSWER
replied on May 23, 2014

No, this has not made it into Workflow yet. You can "sanitize" the token used in the search by splitting it on the quote and building it back up with a set of 2 quotes using the token dialog: %(Entry Path#@Split(")@##[""]#). Or you can use a script to replace the double quotes with double double quotes.

1 0
replied on June 2, 2016

Miruna has this issue been addressed in Workflow yet? Can you tell me what versions of Workflow still need to use this work around?

 

Thanks!

0 0
replied on June 2, 2016

It's been fixed for 9.2 by adding 2 token functions: Escape Search Name and Escape Search Phrase. The first one handles things like field and template names and the second one handles values.

1 0
replied on June 3, 2016

Thanks for the update!!

0 0

Replies

replied on May 27, 2014

That is exactly what I needed. Thank you so much Miruna. You are a wonderful asset to Laserfiche! :)

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

Sign in to reply to this post.