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

Question

Question

Replicate Entry Not Replicating the Entry

Workflow
Updated October 9, 2017
asked on June 13, 2017

I have a simple workflow with a find entry activity that is referencing an entry id. After it, there is a Replicate Entries activity that takes the entry from the find entry activity and replicates it to a different repository.

When I run the workflow, it finds the entry and says everything completed successfully, but there is no entry in the destination repository. If I tell it to put the replicated entry in a subfolder, it creates the subfolder, but no document.

The two repositories are on 2 different Laserfiche servers. The destination and workflow server are on Laserfiche 10.2.1. The source repository is on Laserfiche 10.1.1.320.

Anyone know of why it might not be replicating the entry?

1 0

Replies

replied on June 13, 2017

Any warnings in the instance details?

0 0
View 4 previous replies
replied on June 13, 2017

There is one warning from a conditional sequence, but the instance history shows that it moves past that to the replicate entries activity.

replied on June 13, 2017

No warnings.

0 0
replied on June 14, 2017

does your workflow user have permissions to the volume it is trying to place the document into?

0 0
replied on June 14, 2017

Yes, I logged in as the workflow user to verify I could create a document in the volume. Are there rights that need to be applied to the workflow user in the source repository?

0 0
replied on June 14, 2017

It looks like the user has rights to create the folder specified in the activity, so it could be inheriting rights from the parent folders. I would expect the Laserfiche server to throw errors importing the briefcase into that folder if it was a rights issue (replicate entries briefcases docs from the source and imports it into the target repository behind the scenes).

Are you sure the document creation doesn't trigger a workflow in the target repository that whisks away the document before you get a chance to see it?

0 0
replied on June 14, 2017

Positive. I have even done a search for new documents created this week and there is nothing. It is a new repository that is not live yet, so it would be the only one.

1 0
replied on October 9, 2017

Hey Blake,

Did you ever figure this out or get an answer? I am getting the same results with no explanation.

0 0
replied on October 9, 2017

I believe the issue was related to security tags.

1 0
replied on June 14, 2017

So it looks like what is happening is a folder is getting created in the destination repository with the same name as the document being retrieved from the source repository, but the document itself is not being migrated over. Why would it be creating a folder instead of the document? I have verified that the entry is indeed a document and not a folder in the source repository.

You are not allowed to follow up in this post.

Sign in to reply to this post.

Details
Related Posts
Loading ...