Error after operation Document.Move

[Corinne_]

Hi, I think my problem is that I don't understand Document.Move operation result or don't know to use it. Here is my "simple" automation chain :

- Context.FetchDocument
- Document.Move:
    target: "@{Document.parent.path}/archives"
- Context.FetchDocument

I get a NoSuchDocumentException after automation chain execution. What is wrong ? Is it because Document.Move does not return the moved document ? And how to avoid this behaviour ? I can't find a simple way.

It is the same described here with the difference it is systematic.

Thanks in advance

[Antoine_Cordier]

Hi, can you try without those quotes in your target parameter ?

[Corinne_]

Studio doesn't let me do that :

Validation error: : JS-YAML: bad indentation of a mapping entry at line 3, column 13:
        target: @{Document.parent.path}/archives

[Antoine_Cordier]

I don't understand, I've just been adding a Document.Move operation with @{Document.parent.path}/archives as a value for the target parameter and Studio was OK with that. Goog luck.

[Corinne_]

yes, in the "visual" automation chain editor there is no quote, if you switch to the script editor (from which I copied to my message above) there are some quotes.

[Antoine_Cordier]

Oh sorry, though what document do you want to fetch in your last instruction ?

[Corinne_]

The moved document. The error desn't happen during Fetch operation but on the user view refresh but I can't find a solution to avoid that.

[Antoine_Cordier]

Maybe you are trying to fetch a document that has been moved. The move operation returns the moved document as an input for the next operation in your chain so I guess this fetch thing is unnecessary.

[Corinne_]

With or without Fetch I get the error. I tried "Seam.NavigateTo" without success. I don't know what to do.

[manuek_]

Hi,