As I have a requirement to migrate the xsodata service from on-prem to CAPM based on cloud foundry. One of the .xsodata file contains an auto generated ephermal key which is based on:
how this can also get created in CAPM's entities? I could not find any solution for its implementation.
My table in database does not contain this GenID so I added a before hook in my-srv.js and exposed the entity using req.target['elements'].
Then removed the GenID using delete req.target['elements']['GenID'] and so it got removed from the SELECT statement.
BUT - CAPM still adds ORDER BY GenID ... statement at the end of the SELECT query which still fails and there is no way to control the removal of default sorting on keys.
My idea was to remove the GenID from srv.before method, run the query and add some random UUID to it inside srv.after.
A gentleman has also encountered this issue:
Is there any way out to solve this problem?