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

Question

Question

Search Repository Activity, including all subfolders

asked on August 20

I am using a Search Repository activity to look for an entry (from a form process). The below is my current search syntax and it currently works if the Dept and Division are unchanged. 

{LF:Name="*", Type="D"} & ({LF:LOOKIN="\PUBLIC\Job Descriptions\%(RetrieveFieldValues_Department)\%(RetrieveFieldValues_Division)"}) & {[Job Description]:[Division] = "%(RetrieveFieldValues_Division)", [Department] = "%(RetrieveFieldValues_Department)", [PCN] = "%(RetrieveFieldValues_PCN)"}

However, if the Dept or Division is changed on an update form, it doesn't pull back an entry. Is there a wildcard or other meathod to have this search syntax search through all subfolders for an entry?

I tried the below syntax, however it didn't find an entry which did exists in a subfolder. 

{LF:Name="*", Type="D"} & ({LF:LOOKIN="\PUBLIC\Job Descriptions\"}) & {[Job Description]:[Division] = "%(RetrieveFieldValues_Division)", [Department] = "%(RetrieveFieldValues_Department)", [PCN] = "%(RetrieveFieldValues_PCN)"}

Below is an image of my current workflow which does work IF the Dept and Div remain unchanged. I would like it to search for the PCN through all subfolders in the Job Description folder and take the appropriate action. 

 

0 0

Replies

replied on August 20

Have you tested the search syntax in the client?

The advanced search has a parameter to exclude subfolders, so they should be included by default.

{LF:LOOKIN="Repository\Folder", SUBFOLDERS=0}

2 0
replied on August 21

Thank you for your response. I went back and played with the search syntax ensuring the Include Subfolder button was checked and thinning it out to only look for the PCN and it is now pulling in the result I expected.

{LF:Name="*", Type="D"} & ({LF:LOOKIN="\PUBLIC\Job Descriptions"}) & {[Job Description]:[PCN] = "%(RetrieveFieldValues_PCN)"}

Thank you for your input and inspiration!

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

Sign in to reply to this post.