Dear community,
we are connecting one cap service to another to access and also maintain their entities. this works fine by
1) following the setup steps as documented in capire Consuming Services | CAPire (cloud.sap) (-> For a Remote CAP Service)...
Dear community,
we are currently trying to deploy a .hdpreptask via the Business Application Studio (BAS). The remote source was already defined and could be accessed from our target source via virtual tables. the next step is to have a replication...
Dear Community,
we are having the following entity model in our database. Our intent is also to keep history of changed records which is why we integrated the HISTORY entity as associated entity. for the HISTORY Table we use hdbsystemversioning. th...
Dear Community,
I have two SelectionPresentationVariants as Tabs for my List Report View in my CAP based Fiori Elements App.
I followed the implementation from here:
https://github.com/SAP-samples/fiori-elements-feature-showcase#selection-pres...
Dear all,
in our current app we use an OData v2 and v4 model which are both working fine locally with the v2 proxy and the suffix "v2". When deploying this to the portal service in your space on the SAP BTP the OData v2 metadata is not loaded and t...
Hi smarten,thank you for your quick reply.I thought so too and tried several szenarios already with Side Effects. But none of it worked yet. I always had to hit the Go Button.See Code below. Can you see any error?one sideeffect for the action itself:...
hey nicorunge,thanks for your comment my destination service instance is already bound to my cap service. Did you face the same issue with a v2 odata service? I assume my xs-app.json has to be adjusted in some way..
Dear monokizsolt7inside the object page we are currently trying to implement a valuelist which enables the user to select multiple values. In your screenshot it looks like you made this work. Could you further explain how you did this?the Question be...
Hi kishannaicker,thank you for the answer:)for fiori elements/CAP the following annotation works:annotate service1.ENTITY with @(
Capabilities: {
FilterFunctions : [
'tolower',
],
}
);
