Hi,
We use computations in the ModulF project to, for example, save a combined address in our document model (e.g. Musterstraße 21, 12345 Musterort). We recently updated to a12 version 2022.06 and after the update the computed field gets lost after saving the document. The question would be where this field could possibly get filtered out? Why is it missing in our overview despite being send and saved correctly?
Kind regards
Nick
In version 34.0.0 DS stopped persisting transient field by default. If you want to re-enable this behavior, please set mgmtp.a12.dataservices.documents.validation.persistTransientFields=true
Please be aware that transient fields are not meant for persistence therefore I would suggest reviewing usage of transient fields in your project.
But wouldn’t it be the better strategy to recompute the fields again (in the backend) before you use the document for some automated purpose - because you never know if the input fields may have changed (and don’t trust the client)
In version 34.0.0- DS is always executing compution by default. We are introducing options for a more fine-grained configuration (compute per model) in 34.2.0 but the computations are still executed by default.
I believe the problem is not with computations here but with transient fields which kernel filters out during serialization and therefore we do not know about them on the DS side and therfore we cannot index them.