CAP; UPDATE method doesn't trigger READ hanlder after function _readAfterWrite

[alicegavanelli]

Hallo Experts, I have an issue about READ handler.

I have an Entity with calculation fields. In order to set these fields, I have implemented READ handler.

Triggering a GET request everythings is ok: fields are calculated.

Triggering a PUT request in order to modify entity’s data, fields are empty.

CAP after update runs _readAfterWrite function; this function re-loads entity’s data from DB correctly. After this function, CAP should trigger my READ handler, but it doesn’t.

As a result my calculated fields are empty.

Any ideas on how to solve this problem?

Best regards.

Alice

[sergei-u-niq]

you could try putting your code in after-READ, and see if it is triggered then.

Also, you could use same function _setDscriptions in after-UPDATE (same as in after-READ. note that after-READ and on-READ have different parameters)

[alicegavanelli]

Thank you Sergei for you answer.

I have already try to put my code in after-READ and it is triggered only in GET calls.

With PUT calls, CAP triggers after-UPDATE but before function _readAfterWrite so the result is incorrect. Calculeted fields are empty.

Moreover in CAP's documentation you can see this:

[alicegavanelli]

With a PUT call, CAP triggers these events in that orders:

1. srv.ON (event UPDATE)
2. srv.AFTER (event UPDATE)
3. _readAfterWrite

Never call after-READ or on-READ.