Using an ION API in a dataflow

Good Afternoon,

I am looking at making an ION API call in a dataflow. Is there a way to reference data from the inbound BOD after the API call in the creation of Process BOD back to CSI.

Example: CSI ShipToPartyMaster Sync BOD is used to make a call to Salesforce. Salesforce returns an ID. I need to send a Process BOD back to CSI containing the Customer Info from the Sync BOD along with the ID from Salesforce.

Thanks

Jeff Busch

Find more posts tagged with

ION Connect

Accepted answers

Legacy Contributor

Hi Jeff -

There are two ways that come to mind if you are in the OS multi-tenant:

1) ION API Flows

like so:

where the api flow can be something simple like:

With API Flows you can design your output in the "API Flow Properties | Response" tab to any JSON structure you want to return and pass back parameters from the input as well as value any results from the apis. The ION API connector can then create aBOD from JSON.

2) Merge (this requires elevated licensing)

you can merge individual elements from the api to fields in the source bod, or invoke a script to use python to handle the merge/transformation

All comments

Legacy Contributor

Hi Jeff -

There are two ways that come to mind if you are in the OS multi-tenant:

1) ION API Flows

like so:

where the api flow can be something simple like:

2) Merge (this requires elevated licensing)

you can merge individual elements from the api to fields in the source bod, or invoke a script to use python to handle the merge/transformation

Legacy Contributor

Hi Jeff,

you can use workflow to call ION API instead of API connector in the data flow.

Data flow

Workflow

Inside the workflow use output parameters and map your salesforce API response ID.

Finally from dataflow, you can map these output parameters into your original BOD attribute.

Hope this will help you.

Thanks

Rajitha

Jeff Busch

David,

Great Stuff. Thanks for the information.

Jeff

Jeff Busch

Rajitha,

This is how I am currently handling it. When processing a large bulk of data, the processing of the Workflow is becoming a performance bottleneck.

Thank you for your suggestions.

Jeff

Legacy Contributor

Rajitha / all

I just need to point out that the WF solution is not a good idea and not the best practice or indeed not even a valid use case for WF - WF are designed solely to interact with users, sending tasks or notifications and waiting minutes, days, weeks for responses and moving on to following steps - for approvals or some similar business case. The existence of API's is there to allow enrichment in that context for low volume calls - for example to pull a description of an item when all you have is the code and you want a more useful message for the end user. Anything integration based should go through and use the data flow and API flow capabilities.

sorry to be the negative one but as Jeff points out you will find that you hit bottlenecks and potentially have issues when using WF the wrong way - as tempting as I know it is at times :-)

I hope this is useful to people and not taken the wrong way - I just want people to know the best options to use for the best solutions

Legacy Contributor

Hi David,

I've created ION API Flow and once it activated I can see it on Infor ION API Gateway. But when I try to add that API into data flow using API connector. Which is not available in API Connector. Is there any reason for this?

Thanks

Rajitha

Jeff Busch

Rajitha,

was the ION API Metadata refreshed?

Jeff

Jeff Busch

David,

I have another one that you might have encountered and might have some guidance on.

My ION API call is requiring a 'Patch' Method.

I can successfully test the ION API Call.

This is not an option in the API Flow. I have tried to use a Put and Post in the API flow but have been unsuccessful.

Any words of wisdom?

Here is the error:

Message: Failed to call *******. Code is : 500 Error: Failed to invoke ionapi task for the APIFlowId: ***** due to: com.sun.jersey.api.client.ClientHandlerException: java.net.ProtocolException: Invalid HTTP method: PATCH

Jeff

Legacy Contributor

Jeff, Patch verb support should be in 2021-03 update. Thanks.

Legacy Contributor

Also, the api flow verb doesn't half to be the same as any given verb of an api call made in the flow. so you can have a post or put verb for the flow and inside the flow call patch or get or whatever.

Jeff Busch

That was my thought as well.
This is the error message when I tried that.

Copyright © 2025 Infor. All rights reserved.