Currently the replicate entries activity in Workflow can only give you the entry ID of the output parent folder. It would be very beneficial if it could also give you tokens related to the document that was created in the destination repository such as it's entry ID.
Question
Question
Enhancement Request: Ability to Retrieve Entry ID from Entry Created from Replicate Entry Activity
Replies
We can look into it, but it's not as straightforward as it sounds. Replicate Entries can take an entry listing, like the results from a Search Repository activity.
Miruna,
From you're reply I'm not sure you understood the request correctly. The idea would be that after the entry has been replicated to the destination repository, I could use another activity such as Assign Metadata and point it to the output entry from the replicate entries activity. Currently I can only get access to the parent folder information.
I understand that may not be straight forward though as you would have to query after the entry is created to get that information, but it would be very helpful.
Right, but currently Workflow doesn't know if you're replicating one entry or 100,000 at a time.
The replicated entries generate entry created events in the new repository, so you can get to them from that side.
I understand what you're saying now. If there is a way to add it to the activity that would be great. If not, I can understand and we will find ways to work around it.
Hey @████████ and @████████
Did you ever find ways to work around this? We are trying to put together a workflow that moves W-9's from one repository to another, then back. It will just be one entry per workflow, but I haven't found the best way to find the entry once I replicate it to the other repository. Any guidance or info would be greatly appreciated. Thanks!
This was a while ago, but if I remember correctly we ended up writing the data to a database that include the entry id from the starting repository along with the entry name and other metadata that was needed. Once the entry was moved to the new repository a second workflow kicked off and performed a lookup to assign the metadata as needed.
Thanks for the quick response, Blake. I was kicking it around all yesterday afternoon, and right after asking, I figured out a way.
For the destination folder on the replicate activity, I used a unique folder name, and then even though it is only one entry, used find entries in the destination folder, and then for each entry. Had to do this twice, but it works great. Again, I appreciate your willingness to help.