Hello CAP team,
I'm getting the error "SQLITE_ERROR: ambiguous column name: ID", when following an association witthin a where-condition. Take the following entities as an example:
entity db.Products {
key ID : Integer;
name :...
Hi All, When importing a service definition with cds import and running cds watch, then sometimes mocking for the imported service is not working. Actually, it seems to be an alternating issue. Restarting the watch-server in sequence, let mocking be ...
I'm using an object page with Fiori Elements and OData V4. I only have edit/create buttons on an object page if I'm using Draft Mode. Is there a way or plans for avoiding using drafts and still have edit/create capabilities?
( pdominique-bio : fyi)...
I'm using the Node.js Stack of CAP. I'm using the @odata.draft.enabled annotation for an entity with a key 'ID: Integer'.
The 'cds build' command outputs warnings like "WARNING: Entity key element should be of type "cds.UUID"". Actually, my Fiori v...
I'm using a virtual field in an entity model, like
entity Products : {
...
virtual margin : Decimal(9, 2)
...
}
When building a draft enabled v4 UI on CAP Node.js with Fiori Elements, I can edit Product details on an object page (margin f...
Hi Benjamin,"cds build" solves the problem, that the deployed srv-module has all cds models available, including those which you've placed into your app-folder. Therefore, the CAP-server can generate all OData-metadata including UI annotations.You ha...
HiThe "cds build" command has been made to solve this. It generates the folder "gen/" which has folders (modules) in it, which can be deployed to CF. The "gen/srv/"-folder contains a compiled csn.json which incorproates any cds-models contained in th...
Hi Juanjo,Approuter is an important component of a complete application in the Cloud Foundry environment of SAP Cloud Platform. It is the frontend server playing various roles which are nicely described in this blog. Authentication is the most obviou...
Hi Juanjo,As shown in the post you are referring to, the CORS-configuration in mta.yaml must be part of the approuter module in mta.yaml. CAP (configured via the srv-module) does not know about CORS.Regards, KK
