Back to basics with SAP Cloud Application Programming Model (CAP) - part 12

[@MikhailLukyanaulukcad]

Thank you DJ for your video lesson! It was brilliant to get deep understanding how to use custom logic. As you had restricted time, you were not able to finish with `return next()` but it is ok, missing that you helped me with understanding many other things in CAP. So, everything is clear! Thank you, once again. looking forward watching your new video lessons!

[@DJAdams]

Thanks Mikhail, and you're welcome!

[@machineniv]

Hello @sapdevs @DJAdams Could you please make a session on CAPM with Typescript setup and custom logic and unit testing with Typescript. I do not find much info anywhere. It would help most of them. Thank you.

[@sapdevs]

Hi there - this may be some time coming. I'm personally not a huge fan of TypeScript so it's not on my immediate radar right now, there's plenty more CAP stuff to cover before I get to that :-) [dja]

[@piyushgupta4252]

Thank you DJ for the amazing session! I have a question regarding Associations in anonymous compositions. Is it possible to expand on navigation property 'book' inside composition 'Items' in the example covered in the session? I tried it using odata/v4/bookshop/Orders?$expand=Items/book but it gives a 400 error saying 'Expected uri token 'STAR' could not be found in 'Items/book'

[@sapdevs]

Yes, with V4 the $expand syntax has been, err, expanded :-) This may help: github.com/qmacro/odata-v4-and-cap/blob/main/slides.md#improved-expand [dja]

[@ilhanilhanDev]

Nice!

[@sapdevs]

Thanks!

[@wiseskeshom4673]

Thanks DJ for a great session as always. I just finished a session in offline mode. Today I found something quite interesting, or I just did something wrong haha. If I just comment out the following statement from the Orders entity (changed to anonymous inline aspects instead). Items : Composition of many OrderItems on Items.parent = $self; but I leave an explicit declaration of entity OrderItems there in the schema (not comment out). @cds.autoexpose entity OrderItems { key parent : Association to Orders; key pos : Integer; quantity : Integer; book : Association to Books; } What happened was, file Orders.Items.csv was not created when I run command: cds add data. I had to remove the definition of entity OrderItems (above statement) then file Orders.Items.csv was created. I am not sure this is normal behavior of the how the cds add command works or it is just because of something wrong in my code.

[@sapdevs]

Hi Wises, interesting! I tried this and both org.qmacro-Order.Items.csv and org.qmacro-OrderItems.csv were created in db/data/, as expected. What version of cds do you have? Perhaps you can share the complete code on e.g. gist.github.com or something? [dja]