Calling a custom/standard projection action directly via Postman works fine, but calling the exact same projection through a file-based integration (FTP-in, routed via a Routing Address of type Projection) fails with a generic JSON parse exception on the Connect side.

All FAQ questions / Integrations and APIs

Answer

IFS Connect's Projection Sender (a Routing Address of type Projection) only supports Unbound Actions and Functions that have an Input Structure — it can't call a projection that's just an entity set with no dedicated action/function defined (like a plain CRUD-style entity handling projection). If the projection you're calling doesn't expose an appropriate unbound action/function, Projection Sender simply isn't the right transport for it; use IFS Connect's REST Sender instead, which can call any REST/OData endpoint the same way Postman does.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Integrations and APIs questions