Hello,I have a Fiori Elements app (List Report and Object Page) built with a managed, draft enabled ABAP RAP business object, exposed in an OData V4 service. The root entity includes an attachment (LOB) field. When I upload an attachment via the Obje...
Hello SAP Cloud Integration experts,I’m currently working on decomposing a large integration flow into smaller, modular flows that communicate via the ProcessDirect adapter. My goal is to make the consumer integration flows as dynamic as possible for...
IntroductionIn SAP Cloud Integration, receiver adapters are crucial for enabling communication with external systems. When integrating with an OData API, developers can choose to use either an OData (V2/V4) receiver adapter or an HTTP receiver adapte...
I encountered the same problem. Initially I thought it was caused by a size limit in the attachment (around 32 kB), but it turned out that it was actually a size limit in the header that I used to create that attachment.I solved this by creating the ...
Eventually I solved this using a side effect in the XML-annotations with the attachment as both the source and target field:<Annotation Term="Common.SideEffects" Qualifier="fileUploaded">
<Record Type="Common.SideEffectsType">
<PropertyValue Prope...
Hi, I tried this as well (but for object page and filter), but now the field is visible twice in the table settings. For the field on the object page I can use @Consumption.filter.hidden: true, such that it is not shown in 'Adapt filters', but for th...
