A binary or attachment field is rejected for being too large on a projection action — what now?

All FAQ questions / Integrations and APIs

Answer

Treat large binary payloads as needing a different transport than an inline API field — many contracts cap inline binary size deliberately and expect a separate attachment/document mechanism for anything larger. Confirm the documented limit for the specific operation rather than assuming it's a bug.

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