Hello! This problem is confusing me a bit and can't find anything about it.Summary: Strange "entity already exists" error emitted from CAP.
Details below:Our entities look like this (names simplified):
entity Parent : managed {
key ID1 : UU...
Hi,
I'm trying to use sap/cds to build an application. The cds.ql.UPDATE method does not seem to work or I'm missing how it is supposed to be used.
I've replicated the issue on a minimal project started with "cds init" . You can clone this projec...
Hi,
I'm seeing a very strange behaviour with respect to the way `cds serve` deals with dates on filters.
How can I report this to SAP?
Thanks & regards,
Tiago
Hey guys,
I'm wondering if the CDS syntax is expressive enough to be able to project unique values of one entity into another. I can't find examples on this that work with the sap/cds js module.
Suppose we have the Books entity used in the many ...
Hi everyone!
Quick post on how to overcome a frequent problem in C4C development.
The problem:
You can't login in the Cloud application studio due to this error:
You are sure you are not logged in with your user to this system anywhere else.
...
To add to the previous: It joins using both, the issue is only when preparing the draft object for the Parent being edited in that it doesn't consider all keys used to join parent to child, if that makes sense.
@hans-joachim.both Not sure i understand the question. This example would work perfectly if the entity "Parent" had a single key. Because it has a composite key I would expect the child entity to store both of Parent's keys, i.e. PARENT_ID1, PARENT_...
Interesting approach. Thanks for sharing.
I have solved this in the past by having a normal persistent table created.
Before calling the procedure Cap writes into this table with the records tagged in some way and then passes the tag (a string) ...
This worked! The mistake I made was that we had "properties" when it should be "parameters" Noticed the subtle mistake while looking at your example.Thank you so much Gregor.Take care
Same issue here. We had to do the following to workaround it:rm -rf node_modules # they were broken from a previous npm install that failed
npm config delete registry
npm install
Then specify a specific version on the build command as jasonscott sug...
