You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am trying to update our CDS model by using @readonly annotation for one of our fields.
Based on provided documentation Declarative Constraints | capire , I've understood that this will permit to ignore the field value on both Create and Update operation.
My question here is: will this impact deploying initial data for that field for that field using CSV file ? should I expect a regeneration of this table artifact with a different column definition when using @readonly annotation?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hi CAP community,
I am trying to update our CDS model by using @readonly annotation for one of our fields.
Based on provided documentation Declarative Constraints | capire , I've understood that this will permit to ignore the field value on both Create and Update operation.
My question here is: will this impact deploying initial data for that field for that field using CSV file ? should I expect a regeneration of this table artifact with a different column definition when using @readonly annotation?
BR,
Tesnim
Beta Was this translation helpful? Give feedback.
All reactions