Move data to Infor’s multi-tenant cloud faster and reliably with M3 Data Import Tool for Multi-Tenant (MDI-MT)
When can you use MDI-MT?Enterprises can use MDI-MT to move transactional, master, and other data from Infor and non-Infor legacy systems to multi-tenant cloud solution offered by Infor, such as CloudSuite Fashion and CloudSuite Food and Beverage. MDI-MT can also help in any other scenario where an enterprise may want to move data between systems or when it is necessary to make mass updates to data.
Who can use MDI-MT?MDI-MT is a lifesaver for enterprises and system integrators that want to move large volumes of M3 data to the Infor multi-tenant cloud products such as CloudSuite, and for enterprise IT teams that need to move data between entities. MDI-MT supports both backend and web authentication via ION APIs.
A closer look at the user interface and key features of MDI-MT
Figure 1: The intuitive user interface of the M3 Data Import Tool for Multi-Tenant toolA. Process millions of transactions with parallel processing Traditional data import tools process transactions sequentially. MDI-MT can concurrently process large volumes of transactions in batches. For example, if you want to upload 100,000 historical transactions, MDI-MT will arrange these transactions into 50 groups, each containing 2000 transactions, and start processing them parallelly. Assuming that it takes one second to process one transaction, sequential processing will take 100,000 seconds (2.7 hours) to complete the data upload. MDI-MT can upload 100,000 transactions within 33.3 minutes. Using MDI-MT, a leading luxury lifestyle brand in the UK reduced data upload time from days to hours during several critical data migration exercises.
Figure 2: With MDI-MT, a leading fashion manufacturer reduced the data upload time by 83%.MDI-MT can even handle 10 million transactions per run provided that the client, server, and the API can support the load. B. Change the company and division MDI-MT allows you to change the company and division to which you want to upload data. This way, users can upload data without changing the company and division assigned to them in M3. C. Use custom delimiters Similar to the EVS100 program in M3, MDI-MT allows uploading data using CSV (comma-separated values) files. The advantage of using CSV files is that they consume less memory; thus, they can contain large volumes of data and be processed faster. But what if you are importing addresses of consumers to your CloudSuite? A CSV file delimited by commas will not be able to separate addresses from other values. To rectify this issue, you can set a different character such as the vertical bar/pipe (|) or semicolon (;) when generating the CSV file. Most operating systems such as Windows and macOS allow users to change the list separator character from the regional settings. If you use the same list separator character defined in the operating system in the Delimiter textbox, MDI-MT will successfully import your consumer address data. D. Upload data via REST API and M3 Web Services MDI-MT supports uploading data via both REST API and M3 Web Services (MWS). Upload data with an auto-generated template When uploading data using the API, MDI-MT allows you to upload data using a CSV template. To download the template, select the API and click the download icon. When downloading, you can select whether you want to only have the headers or have helpful metadata such as fields, field name, field length, field type, and mandatory/optional nature of a field.
Figure 3: Upload data with an auto-generated templateCover more ground with M3 Web Services (MWS) The ability to upload data via web services is important as the API does not support updating all data. When using web services to upload data, MDI-MT allows you to match the M3 program fields with CSV headers through an XML file.
Figure 4: M3 Data Import Tool for Multi-Tenant | Web Service EditorE. See a summary of the data upload job Once MDI-MT completes uploading data, it shows you a comprehensive summary of the data upload task. If any, the summary includes the number of records that failed to upload and points you to a CSV file where you can get granular visibility into each record. If you select Log OK before executing the upload, the summary will include details about the transactions that were successfully processed. F. Check the sanity of data before uploading If you select the Test checkbox before executing the data upload job, MDI-MT will only upload the first five rows of the dataset. This allows you to perform a sanity test on the dataset before uploading large volumes of transactions. If the test upload completes with errors, you can fix the errors (e.g., add the missing columns) and re-run the upload job without enabling the test option.