Daniel Hutzel

Good idea, we should do so 👍

Still work in progress ... :) Partly because it uses some convenient shortcuts we just added to be published with upcoming release, like this one: ```js class DatabaseService { ......

[Latest commit](https://github.com/SAP-samples/cloud-cap-samples/pull/196/commits/02f19e295dd720ce440b8ca54f41cc9d4b520f64) requires https://github.wdf.sap.corp/cdx/cds/pull/2114

Seems to be solved meanwhile. → running `cds w fiori` (or `cds w bookstore`) works as expected, with `OrdersService` being mocked: ```js [samples] cds w fiori cd fiori cds serve...

Should add: it's pretty poor that OData doesn't support creating multiple rows by one request other than through `$batch` requests. CAP does btw: ```js INSERT.into (Books) .entries ([/* ... →...

One more comment: as also discussed in other forums, a better way to do bulks inserts in OData would actually be through actions accepting arrays of entities or deep inserts...

Yes, maybe we need to clarify its usage: - during development / experiments you should work with monorepo setup → `node_modules` in root only - local installs are required for...

Please don't downrate this. it is really very strange API design. I'd expect an API design like that: 1. we should only have to use `http-client`. 2. which should provide...

I think we should go for calculated fields instead of the programmatically filled field controls: https://github.com/SAP-samples/cap-sflight/pull/50/commits/ebbfe15457ddf58db9be92738648601894bcf295 Fix https://github.com/SAP-samples/cap-sflight/pull/50/commits/75c0f721e0b50c27e4bf25c445d425921fff413c was in general wrong before, I think. With calculated fields it is...

Works in Sflight but not because of that annotation but apparently because of some other, maybe UI.Hidden. Tried the same in bookshop and that failed