Sorry, no diagram.
As already stated this is going through the same object structures and processing as for flat/XML files. So, in that sense, it is fully supported as all this is doing is converting the MXDataload sheet into XML and processing that XML through the Object Structures.
If you use a flat file, you must have the Object Structure marked as supporting flat files meaning you will have to create an alias for each conflicting column, whereas, with the MXLoader it converts to XML and therefore no issue and saving you some gried.
The MXDataloader is fast and visual, whereas, using a flat file import you have to look at the import processing to see if it was successful.
The flat file can be run via cron task meaning you can simply add the sheet to a folder, then cron will then pick it and process it. Great to user isolation as they don't need to have a Maximo license.
Hope that helps.
------------------------------
Regards,
Craig Kokay
ISW
Maximo Practice Manager
eMail:
ckokay@isw.net.auPhone: +61-411-682-040
#IBMChampion2023
------------------------------
Original Message:
Sent: 10-11-2023 09:27
From: Prashant Sharma
Subject: MxLoader vs Flat File imports
MXLoader is not officially supported but uses the same Object Structures which you will do using Maximo UI Import.
If you draw the diagram internal processing will remains same as when data loading is happening it is going through same layers of processing as Maximo UI Import will do.
Maximo UI Import is not recommended if data amount is high as it impacts Maximo performance while MXLoader have batch load mode which you can play with and load much high amount of data. Same goes for exporting data from Maximo vs MX Loader.
------------------------------
Prashant Sharma
Sedin Technologies
Connect with me @ https://www.linkedin.com/in/psharmamaximo/
#IBM Champion 2022
#IBM Champion 2023
------------------------------