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

Question

Question

searching for documents in Laserfiche within subfolders across our entire repository.

asked on May 24, 2018

Hello All,

 

I didn't really know how to to title this, but here is what I have going on. A colleague of mine is looking to search in laserfiche for all documents that don't have a template assigned to them. The trickier part of this is that the documents have be in a certain folder. The documents in question are located in a clients "02 Account Folder", and within there, the "Confirmations" folder. Once we are looking in there, we can then search for documents without a template.

The client's folders are found in our 00 - Clients folder, and then clients are separated by the beginning letter of their last name (A - Z) within each respected client folder we then have a list of potential folders where "02 Account Folder" can be found. 

 

I'm attaching a file for clarity as our folder structure can be confusing while explaining it. (Also posting the picture in the forum just in case someone can't see either picture)

 

 

Thanks for all the help and for those who look at this.

 

LF Folder Structure.PNG
0 0

Replies

replied on May 24, 2018

It might be possible with advanced search syntax. I'm not sure I've fully understood your folder structure. Are there any other folders named "Confirmations" that are also in the repository, that you don't want to search? If not, you could search for documents with no template that have a parent folder named "Confirmations":

{LF:TemplateID=0} & {LF:ParentName="Confirmations"}

Another possibility is that the folders you're interested in are the only ones named "Confirmations" within the "00 - Clients" branch of your folder tree. In that case, you could add an additional clause to make sure that you search only the descendants of "00 - Clients":

{LF:TemplateID=0} & {LF:ParentName="Confirmations"} & {LF:LookIn="00 - Clients", Subfolders=y}

If you can't do that, you might have to search each path individually. So for each Confirmations folder you might have to do the following (change the path to the correct one):

{LF:TemplateID=0} & {LF:LookIn="00 - Clients\ClientName\02 Accounts\Confirmations", Subfolders=n}

Resources:

2 0
replied on May 24, 2018

Thank you! I will look into this and mark this as the best answer if it works.

 

But to answer your question, we are only interested in folders called Confirmations or Confirmations - Done, depending on what they are called. And It's only within the main folder of 00 - Clients.

0 0
replied on May 24, 2018 Show version history

OK, in that case you could try the following:

{LF:TemplateID=0} & {LF:ParentName="Confirmations*"} & {LF:LookIn="00 - Clients", Subfolders=y}

Note that I've added an asterisk (*) after "Confirmations". This is a wildcard that will include any names that start with "Confirmations", so it would capture both "Confirmations" and "Confirmations - Done".

0 0
replied on May 24, 2018

Does it matter that we only want to look within "02" folders within the "00 Client" folder? I believe right now it's looking in any folder that has a confirmations folder. So it's also pulling in "01", "03" and other folders of that nature. 

 

so with this example. Only interested in the 02 folders. And when we go into the folder further, then we encounter the confirmations one.

 

But otherwise this was a great start to go from.

0 0
replied on May 24, 2018

Is there anything about the Confirmations folder and its contents that distinguishes it from the non-02 Confirmations folders? E.g. does that folder have a different template, fields, tags, etc. from the others?

If not, you might have to do the search individually for each path, as in the third example in my first post.

0 0
replied on May 24, 2018

Nope, there isn't anything distinguishing it aside for the fact it resides in the 02 folder of clients. After speaking to our 3rd party vendor, it was brought up since it's a 2 tier (recursive) search that we may be better off building a workflow to search for these respective documents.

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

Sign in to reply to this post.