MxLoader

 View Only

MxLoader FileEnc file path location defined where?

  • 1.  MxLoader FileEnc file path location defined where?

    Posted 13 days ago
    Edited by Christi Eades 12 days ago

    Using MxLoader 8.5.2 and MAS 9.0.27.  Trying to use FileEnc to download attachments in MxLoader, specifically FileEnc:DOCINFO.DOCUMENTDATA or FileEnc:DOCLINKS.DOCUMENTDATA. My question is where is the FileEnc path location defined?  When the loader runs, I get data for PO (Parent Object), DOCINFO, but no data for DOCLINKS in my first testing scenario.  in my send scenario I created an OS directly to DOCLINKS with PO as the child.  In this example I was able to get data for both DOCLINKS and PO, but nothing returned for FileEnc:DOCLINKS.DOCUMENTDATA and no folder was created in the location of the MxLoader workbook.  I tried creating the folder as the sheet name and as the OS name, but did not work.  Can not figure out where/how the FileEnc folder is defined to receive the downloaded attachments?

    Testing 1, Parent Object PO, Child Objects DOCLINKS and DOCINFO. Nothing returns for DOCINFO.DOCUMENTDATA in loader and no folder is created in the loader file location, all fields are included in the OS(I tried DOCLINKS.DOCUMENTDATA here as well, same result): 

    Testing 2, Parent Object DOCLINKS, Child Object PO. Nothing returns for DOCLINKS.DOCUMENTDATA in loader and no folder is created in the loader file location, all fields are included in the OS: 

    I have included a screenshot from the example from Bruno on how to download attachments using Enc for binary files: Binary and text files handling in MxLoader 8.5 – Bruno Portaluri (MaximoDev)  Where would the ItemsGet folder be defined?  Is it the name of the sheet in the loader?

    Thanks!

    ------------------------------
    Christi Eades
    City of Fort Worth
    ------------------------------



Newest Episode
Ep. 6 | Automation Script Do’s and Don’ts in IBM Maximo

Watch Steven Shull share practical do’s and don’ts for using automation scripts in IBM Maximo, including when scripts make sense, what to avoid, and how to keep them simple, tested, documented, and supportable.

MORE by Naviam Episode 6 cover
Watch Episode 6
Also available: Ep. 5 | Make Manage Feel Like Home with Configuration, Not Customization