Integrate M3 with Third Party application using ION API

Hi,

May I know the possible approach in integrating M3 to a 3rd party app using ION API in ION Desk? JSON format will be used to integrate with 3rd Party App

Here's the sample scenario:

A customer is created in M3
OCUSMA is received in ION
The 'Send to API' scenario is selected in the ION API connection point Documents tab
'Map input document to API Request' is selected in Request Body tab

Concerns:

We need to send only the Customer Number, Name and Address from OCUSMA
We need to format this so that it will correspond with the Request Body of the 3rd party API.
We also need to change the object name, example CUNO from OCUSMA will be changed to "CustomerCode" in the Request Body.

How do we achieve the steps mentioned above?

Any inputs will be greatly appreciated.

Best Regards,

Maria

Find more posts tagged with

ION Connect

Accepted answers

All comments

Legacy Contributor

Hey there Maria,

For integration scenarios such as this, the best recommendation would be to utilize standard Business Object Documents (BODs) like the CustomerPartyMaster BOD. This provides an event-driven solution triggered when customer records are added, updated, or deleted from the system. The additional benefit here being that this is a document-driven integration approach and frequently includes most, if not all, the data components your outside app might require.

If your 3rd party application can't handle these canonical XMLs, you have several options to help design the integration flow depending on your needs. The ION Mapper can help automate mapping standard BODs to custom XMLs that can be processed by your app. If you're looking for a particular file format, you can also write custom Python code to transform and enrich data in-flight with ION Scripting.

Kirill Kuchumov

Hi Maria,

There are lots of options to do it.

You can use standard BOD and remove unwanted data in ION script or map.

You can build custom MEC map to pull only what you need.

What is file format for your 3rd party app?

PM me if you need some help with it.

Regards,

Kirill

mpazluna

Thank you very much Mike for your inputs. Very much appreciated.

mpazluna

Hi Kirill. Yes, we will use standard BOD as Mike suggested and create ION script to convert it to JSON format. I don't think we need custom MEC map since all the details are already in the standard BOD. Thanks anyway.

mpazluna

Hi Mike,

It seems ION Scripting is not needed, we used the element "IonApiRef" in the path expression to define the values for the Request Body and it worked.

Best Regards,

Maria

Thomas Kneidl

Hi Maria,

this will not work for all cases as it is not type-safe, e. g. if you provide a string looking like a numeric value, the JSON-Parser will convert this to a number and your API-Call might fail.

So, IonApiRef might work, but there are cases where you have to go with scripts.

Best regards

Thomas

mpazluna

Hi Thomas,

Thanks for the information. We will consider using ION Scripting if needed.

Best Regards,

Maria

Copyright © 2025 Infor. All rights reserved.