service projection exposed entities alias, how is it supposed to work?

[former_member630950]

Based on https://help.sap.com/viewer/65de2977205c403bbc107264b8eccf4b/Cloud/en-US/4eb171573f5947518a9b0800299..., where it says under Exposed Entities:

service CatalogService{
  entity Productas projection on data.Products{
    *, created.at as since 
  } excluding { created };
}

So, I'm trying (as a proof of concept) to alias the required input fields. I've added this to my service.cds.

entity MyEntity as projection on api.MyEntities {
  *,
  someField as somethingElse
} excluding { someField };

The generated $metadata also reflects this.

However, when doing a GET or POST on /v1/service/MyEntity, I get a 500 error and the console is telling me:

[2019-09-04T12:21:38.204Z | ERROR | 1832755]: invalid column name: SOMETHINGELSE: line 1 col 282 (at pos 281)

Does this feature not work or am I using it incorrect?

[mariya_yordanova · Accepted solution]

Hi Bastiaan,

we reproduced your problem. This is a bug in the NodeJS Runtime. Thanks for reporting it.

We will inform you when the fix is availble.

Best Regards

Mariya

[vitaly_kozyura]

Hi Bastiaan,

The issue is fixed. Fix to be provided with the next release.

Best regards,

Vitaly

[chgeo]

Hi,

please make sure the underlying database is properly set up and also deployed.

Which stack do you use? Java or Node.js?

Is there more detailed logs?

Regards,

Christian

[former_member630950]

Hi Mariya,

thanks for your response. I'll be looking forward to the update.

Best regards,

Bastiaan

[former_member630950]

I'm using the NodeJS stack.

Sadly there's no more logging reported by the Web IDE or the Cockpit.

I've ran this multiple times, even after rebuilding cds files and database, but no luck so far.

cds version used is 3.16.3

Also, the files generated for the db (src/gen/*.hdbcds) just look the same. The 'somethingElse' alias is not reflected in there (which I'm not expecting anyway).

Also, did some additional testing and GET request do work as expected now, but POST's still generate a 500.