Question

Advanced search syntax in workflow - escaping forward slashes

Workflow

Updated February 21, 2022

asked on February 18, 2022 • Show version history

Hi,

I'm struggling with a Workflow that attempts to repeat a search based on a token but the search syntax requires leading and trailing forward slashes in the search string. The advanced search syntax is as follows and works fine in the LF Client:

{[]:[Original Filepath]="*/ABCLIMITED/*"}

If I try the same syntax using a WF token as part of the search repository activity it either doesn't recognise the token when testing (i.e. no prompt to provide a value appears if the slashes are not escaped), or if I use the "//" escape characters the token is recognised but no results are returned which is incorrect.

The search query string in WF reads:

{[]:[Original Filepath]="*//%(ForEachRow_REFERENCE)//*"}

Is there any way around this?

Thanks,

Nigel.

0 0

Replies

replied on February 18, 2022

I think it's the // at the end. You only need to escape the first / because /% will turn the percentage sign into a literal %.

So {[]:[Original Filepath]="*//%(ForEachRow_REFERENCE)//*"} searches for {[]:[Original Filepath]="*/ABCLIMITED//*"} . Try {[]:[Original Filepath]="*//%(ForEachRow_REFERENCE)/*"}

0 0

replied on February 21, 2022

Hi Miruna,

I did try only escaping the first / originally but although it prompts me to enter a token value it returns 0 hits so it must be getting parsed differently to expected. If I hard code the token value it returns 48 hits as expected.

I have a convoluted workaround in place but it runs slower than the original approach so if there is a way around this it'd be a big help!

Thanks,

Nigel.

0 0

You are not allowed to follow up in this post.

Question

Question

Advanced search syntax in workflow - escaping forward slashes

Replies

Sign in to reply to this post.