Question

replicate entry creating a duplicate file structure in destination repository

Version 9 Workflow Search and Retrieval Laserfiche Ideas

Updated August 18, 2022

asked on May 15, 2014

Good Afternoon All,

I've built a workflow for a client that will grab documents older than 3 years and move them into an archive repository, then delete the original document. (See attached image).

The client is using the Manual test / run feature in the workflow designer as there is just too much data to attempt to move at once. He chooses the main folder to run the workflow against and puts it in the search repository object. The process works perfectly, with one exception.

When he tries to re-run the process (because there are sub folders with a LOT of documents) it creates a second, third, etc. copy of the whole folder structure, rather than using the existing structure.

Is there a way to force the Replicate Entry process to use the existing folder structure? I use the preserve folder structure checkbox option to ensure the paths are preserved.

Regards,

Brian

Capture.PNG (9.01 KB)

| Download

0 0

Replies

replied on June 19, 2014

I found the answer and have attached a screen capture of the workflow.

These are the key points:

Set the Search Repository to "All Results"

Set the For Each Entry to point at the Search Repository Output Entries

Set the Replicate Entries Destination to point at the For Each Entry Current Entry Path

Set the Replicate Entries Entries to Copy to the For Each Entry - Current Entry

Set the Delete Entry to point at the For Each Entry Current Entry

Hope this helps someone!

Regards,

Bran

Capture.PNG (11.02 KB)

| Download

1 0

View 2 previous replies

replied on March 17, 2020

I have this exact issue, however I'm not running a search, I'm triggering the workflow with a starting rule, and using the starting entry tokens like you are above. However despite everything I've tried, I cannot get the destination repository to merge folders, it will only create duplicate folders. I think this might be a bug.

0 0

replied on March 17, 2020

Found the cause of this, if the templates between the repositories don't exactly match, then it's assumes things are different and duplicates the folder strcuture.

0 0

replied on August 17, 2022

Running into this same issue. When you say if they don't match exactly... Do you mean both directions? Not just the sources templates have to exist (exactly the same) on the destination?

0 0

replied on August 18, 2022

Yes both must match exactly, in terms of fields, names, types, lengths etc.

0 0

replied on August 18, 2022

Thanks. Wasn't very practical to do this on our end but I did find another way to accomplish this by first verifying if the file(s) exist before running the replicate entries.

1 0

replied on May 15, 2014

Can you please publish a screenshot of the tree structure so to understand where duplication happens and how duplicate folders are named

0 0

replied on May 16, 2014

Here you are. Basically it is duplicating the directory structure in the destination repository.

Capture.PNG (19.91 KB)

| Download

0 0

replied on May 16, 2014 • Show version history

Hey Brian,

This could most likely be avoided simply by adding a Search into your archive repository. Instead of just replicating the entries into the archive, run a search and first try to find the Folder where you're looking to route stuff, followed by a form of flow control. (condition sequence, routing decision, etc.) should be something like this...

Search In Archive:

Folder found? Route stuff there. (you can use replicate entries activity and change the destination to the FullPath of the Search).

Folder Not Found? Create it with the "replicate entries". Then next time you run this search it will follow the "folder found" route if it's already created.

Let me know if you need further explanation...

Tony

0 0

replied on May 19, 2014

Have you checked the security on the folder structure in the target repository? It sounds like the user specified in the connection profile might not have rights to see those folders.

0 0

You are not allowed to follow up in this post.

Question

Question

replicate entry creating a duplicate file structure in destination repository

Replies

Sign in to reply to this post.