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

Question

Question

%(Fields.Doc Type) cannot be resolved in 'Destination' with "move entry".

asked on June 7, 2022

This question has to do with "Route Entry to Folder" vs "Move Entry".

I want to use "Move Entry". 

I copying an entry to a path that uses token that has the value in a Field called "Doc_Type", which might be contain something like Report, Ticket, Cancelation, Application, etc. That's why I want to use Move Entry, because it lets me copy, while Route Entry to Folder does not. Here is the path:

 

 \R1\Employees\%(Fields.Doc_Type)\ is the path. 


This path with tokens works fine in "Route Entry to a Folder", but that only allows me to move it, not copy it. I want to copy it, for which "Move Entry" underlines the %(Fields.Doc_Type) in red and says it "cannot be resolved in 'Destination'. I thought...well, put the Fields.Doc_Type in another token, then try it, but that doesn't work either. The token dialog in "Move Entry" doesn't have that token. I know I have this typed out correctly and the field is accessible because the workflow did fine while in route entry to folder. 

So is it possible to use field tokens within "Move Entry"? Or is there some other workaround? 

 

0 0

Replies

replied on June 7, 2022

The "Route Entry to X" activities wrap a lot of activities into one. Email, Wait for Change, Move, and retrieve field values to name a few.

 

To overcome this,  you need to do is add a retrieve Field Values activity directly before move, then use that token it outputs in your move command.

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

Sign in to reply to this post.