Skip to main content
deeptip2492
deeptip2492
July 2, 2021
Question

Move documents issue

  • July 2, 2021
  • 7 replies
  • 0 views

I am trying to use the move documents smart service in  MNI mode to move multiple documents to a folder. It's  only moving the first document and the next documents are getting deleted from appian. I can't find them by name or document id anywhere in Appian.  When I try to find the document using getcontentobjectdetailsbyid function, it returns this response. 

  • "Content Object [Name: SamplePDF3.pdf, UUID: _a-0000e63c-719f-8000-9bb5-011c48011c48_148201, Parent: , Parent Id: 0, Type: Document, Created by: 00001, Created on: 2021-07-02 06:57:50.0, Last updated by: 00001, Last updated on: 2021-07-02 07:05:39.0, Latest version: 1, State: Active Published, Internal file name: accdocs3/7285/10005248.pdf]"(Text)
    But the document is not visible anywhere - old or new folders.

    Additionally this is only happening on version 21.1 and not on 21.2 

    7 replies

    csteward
    csteward
    July 2, 2021

    Can you share your inputs for this service for document and destination?

    The return from getcontentobjectdetailsbyid appears to indicate the document is available, but with no parent folder.

    deeptip2492
    deeptip2492Author
    July 5, 2021

    In that case, it should have let me search the document by ID or UUID, but it doesn't.

    mikes0011
    mikes0011
    Brainy
    July 2, 2021

    Agreed with Chris - the symptoms you describe seem consistent with what happens when a document is (usually accidentally) moved to a folder with a null or zero ID (thus, really moving the document to no folder).  I'm not really sure why this doesn't error out in Appian, but apparently it doesn't.  I'd bet money on the spot that your MNI configuration is incorrect, probably in some small way.

    deeptip2492
    deeptip2492Author
    July 5, 2021

    I will check the MNI but I still don't get why it won't let me find it by UUID or ID.

    mikes0011
    mikes0011
    Brainy
    July 6, 2021

    I agree, I just happen to know (from dealing with this on my system recently) that it won't work.  However, the "move document" smart service (when fed the doc id manually) *will* work, meaning for any affected documents you can move them somewhere "safe" then interact with them somewhat normally again.

    Terms & ConditionsAccessibility statement