Send M3OutputDocument (XML) to ION

In the October 2026 release, Infor introduced a direct connection point from Infor M3 to ION for sending M3 output documents.

Note: This feature is not enabled by default and is scheduled to become enabled by default in the April 2027 release (2027.04). Until then, it must be manually enabled through CMS975, as described in KB3692409.

Step 1

Create a new service ID in MNS216 and refer to screen shot below. 

Service type must be M3_XML_CSV.

Commun type 7-ION can be seen after enabling the feature in CMS975.

For the Doc Name, I tried to define a object in Data Fabric Data Catalog Object Schemas based on the M3OutputDocument XML structure , but it system returns the below error (MNS209).  It worked when I configure it as AnyDocument.

MSG {"status":"FAIL","code":473,"errors":"Document 'XXXXXX' is not accepted for tenantId 'XXXXX_TST' and logicalId 'lid://infor.m3.m3:fnd'."}

Step 2

In MNS204, select the Service ID created in Step 1 for the document you want to send. Create MNS205 record too. 

Step 3

Then, create the ION Dataflow to receive the xml document. For this post, I've created very simple DF like below. 

• Goto the Connection Points in ION Desk, select m3_fnd connection point. 
• Add AnyDocument to the document of the connection point. 

• In the Dataflow, add Application activity and select m3_fnd  application. 
  
  
  
  
  

Step 4

Test the Dataflow. 

Limitations

Please review the limitations outlined in KB3692409 before finalizing the technical solution.

IDM Printer Alignment Issue

Issue

While supporting my recent technical upgrade project, I found that the customer is using old dot-matrix printers to print Delivery Orders (DOs) on pre-printed stationery. The customer is using the same printer model and configuration across seven different locations.

Out of the seven locations, two locations confirmed that the DO printing works correctly with no alignment issues. However, the other locations experienced different types of misalignment issues, despite using the same printer model, printer driver, driver version, and IDM document.

This indicates that the issue may not be related solely to the printer model, driver, or document template, but could also be influenced by printer-specific configuration, protocol settings, paper positioning, physical printer calibration, or IDM media settings.

Troubleshooting steps

From a solution perspective, I wanted to maintain a single MMS480PF template for all seven locations. With this in mind, we also reviewed the printer-side configurations and confirmed that printer-specific settings—such as page size, orientation, paper positioning, and printer calibration—were consistent across the problematic printers.

Solution

The issue has been resolved after I have done below changes together. 

1. Change the protocol to "Raw" in the TCP/IP port setting. 
   
   
   
   
   
2. Change following parameters in the IDM media setting specific to each printer.
   

Scaling: ACTUAL_SIZE

Enable "Set Custom MediaSize"

Name: iso-a4-custom

Width (inch) : 9.527559

Height (inch) : 11.0236 

Margin from Left (inch): -0.25

Margin from Top (inch): 0.15

to finalize the margin values we have to measure the elements with the ruler. 

How to find this setting in IDM:

• Go to Print option the Infor Document Management, then "Manage Service"
  
  
  
  
  
• Click on the printer ID of the related printer to get the Settings dialog 
  
  
  
  
  

Moving to The Cloud

Infor M3 has taken the approach to move into the cloud by releasing  major version of M3 Cloud Edition (M3 CE) in early 2018. With this release Infor is encouraging customers to move as well, highlighting the key benefits that they are gaining.

M3 Big Picture (courtesy  of Infor)

Key Highlights

• Single Version 
• You will always have one version across your environments. 
• Incremental developments.
• Continuous delivery of new features. 
• To stay "Super Current".
• Automatic Updates
• No more upgrades. You will receive recent updates automatically to make sure the system is up-to-date. 
• Controlled through Toggles and Parameters not to have impact on existing business processes.  
• Scalable
• As it is in the cloud, by nature, we don't have to worry about the load of the system. We can scale the system to fit into out load. 
• Secure
• Infor is making sure the security factor by implementing 3 SD concepts. 
• Secure by Default.
• Secure by Design. 
• Secure by Deployment.
• Extensible 
• Ability to extends existing feature to suit your needs. 

Having said that, practically you will have challenges when providing the solution. For an example, you know the relationship between the hammer and the nail. depending on size of the nail, you have to choose the type or size of the hammer. Like wise, our solutions has to be adjusted accordingly the Cloud concepts. 

However, as the time moves on,  Infor M3 CE will mature to the level where these challenges become insignificant.  

Single Tenant Vs Multi Tenant

In the Cloud, we are talking about Multi-Tenancy.  In short, Multi Tenant is, the System is shared with multiple organizations(tenants), as shown in below diagram.

Single-Tenant Vs Multi-Tenant (Courtesy of  https://www.peoplefluent.com/blog/learning/single-tenant-lms-vs-multi-tenant-lms-security)

For M3 same multi-tenant (MT) principle applies and separation is based on the Tenant ID. The individual organization will have separate Tenant ID, which make sure no overlapping will happens with other tenants.

M3 Solutions for The Cloud

As we are more used to providing solution for M3 On-prem or Single Tenant, working with MT environment may be a paradigm shift. Because, We have to work with the certain constrains, selective technology and tools. 

For an example, we cannot run SQL commands, we used to execute in On-prem version, in MT environment. For me it is hard to work without SQL (similar to the feeling that my both hands were tied and ask to develop) , but due to this constrain I have to think about differently.  

What is next

M3 world is changing and Infor is investing in M3.  We should be ready.

I'm planning publish few posts with regards to M3 MT technical solution in future.