Background - we are using the deprecated compass from Infor ION/DataLake API to query data from M3 for our Initial Load. However, there is a note that this will be deprecated next year. There is a suggestion to use the similar compass from DataFabric instead. However, one of the things that is causing issue is on API that submit jobs (compass/v2/jobs). The one in DataFabric only accepts text/plain and doesn't accept application/json anymore. This is fine until you use that API in the API Flow since it is not being recognized in the Request Body thus, unable to properly set a specific query. In the deprecated compass (from ION), this doesnt have any issue since it can accommodate both types (json or text/plain).
So my question is, is this a bug on the API Flow not being able to recognize request or response in text/plain? When I use the same API in Connection point, it is able to recognize text/plain types. Not sure why orig one was deprecated when this new one is unusable in some areas.
Steps to recreate -
- go to Connect - API Flows
- Insert a new API from DataFabric
- Search for compass/v2/jobs
- Go to Request Body - content type is blank and disabled
