Client-side only property #422
-
|
Hey Community I need help. I have a property that's only available in the client data model. Further, that specific entity is only writable for particular user roles in the backend. But that client-side property can be written by any user. This causes an issue, as when that property gets updated, the sync toolkit detects a change and tries to synchronize data, and the backend returns 403, as the user does not have permissions to modify the entity. Is there a built-in mechanism to exclude certain properties from causing a sync? I know there's a workaround and I could potentially put that property into another table that is not synced. But I wish there was a way to achieve this without the added complexity of a separate table. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
Have you attempted to JsonIgnore it on the client-side? |
Beta Was this translation helpful? Give feedback.
... and after thinking about what is behind the logic here, this won't work - your value will be overwritten with null/default when the item is synchronized. You should have a local-only table for this data and do a join when reading it