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

Question

Question

Search for documents based on wildcard data in folder path

asked on February 18, 2014

Is there a way to use advanced search syntax to search the documents full path.

 

For example, I'd like to return all documents that have *California* somwhere in their folder path or file name.

 

I know I can return any document and folders with that name, however I'm using workflow to process the results so I don't want the folders with that wildcard, I want the documents within those folders and their subfolders. 

 

Hopefully this is clear.  

0 0

Answer

APPROVED ANSWER
replied on February 18, 2014 Show version history

If I understand you correctly, the following syntax should do what you want:

 

{LF:ParentName="*California*"}|{Lf:Name="*California*",type="DFS"}

The first clause, ParentName, will return all documents and folders that whose parent folder has California somewhere in the name. The second clause, Name, will return all folder, documents, or shortcuts with California in the name.

 

Example folder structure to help demonstrate what Parent Name does:

 

RepoRoot

  • California
    • Subfolder 1
      • Subsubfolder
      • Document on California 1
    • California subfolder
      • Document on California 2
  • Federal Folder
    • Subfolder 2
      • document on California 3
    • California Subfolder
      • Laws document

 

{LF:ParentName="*California*"} alone will return:

 Subfolder 1, California subfolder, Document on California 2, and Laws document

 

Note that ParentName does not iterate through subfolders. That is, Subsubfolder will not be returned, since it's direct parent does not have California in the name.

4 0
replied on February 18, 2014

Great! I'm not sure that it will need to iterate through subfolders of qualifying folders. 

 

Tested that out and it works well. 

 

Thanks Brianna!

0 0

Replies

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

Sign in to reply to this post.