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

Question

Question

Search Repository tool for metadata field

asked on February 4, 2021

I'm trying to use Search Repository to look into a particular folder and find out if an employee has a completed inspection form.  I'm using this Advance Syntax with Search Repository:

{LF:LOOKIN="BPD\Support Services Division\Inventory & Readiness\Vehicle & Uniform Inspections"} & {LF:Name="*", Type="S"} & {[]:[Employee Name]="Smith, John"}

Field Name is "Employee Name"

Metadata in the Field is "Smith, John"

I know there is a entry there and I have tried it multiple ways with no returns.  When I remove the metadata syntax I get the proper amount of docs in the folder when testing the search repository.  Any help please?  Tjamnl 

Capture.JPG
Capture.JPG (51.27 KB)
0 0

Answer

SELECTED ANSWER
replied on February 4, 2021

You're looking for shortcuts (Type="S"). They don't have metadata. So those criteria can't be true at the same time.

0 0
replied on February 4, 2021

Even If I have the box checked "If an entry is a shortcut, use document or folder that it references"

0 0
replied on February 4, 2021

As long is the shortcut is in the same folder which seems unlikely

0 0
replied on February 4, 2021

"If an entry is a shortcut, use document or folder that it references"  means that if the search returns shortcuts, WF will resolve them for the entry. But this search won't return any results because the 2 criteria are incompatible.

0 0
replied on February 5, 2021

Hello Jhon, query: the BPD corresponds to the name of the repository, if the answer is yes, try removing it.

0 0

Replies

replied on February 4, 2021

Try logging in to to the client and search with the same exact syntax, if the file shows up check the security to make sure the workflow service user has rights to it. If it doesn't show up, rebuild your search syntax using the search toolbox.

0 0
replied on February 4, 2021

Just tried using the client - same thing.  

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

Sign in to reply to this post.