Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 4 additions & 6 deletions guides/services/constraints.md
Original file line number Diff line number Diff line change
Expand Up @@ -368,13 +368,11 @@ service Sue {
}
```

In addition to server-side input validation as introduced above, this adds a corresponding `@FieldControl` annotation to the EDMX so that OData / Fiori clients would enforce a valid entry, thereby avoiding unnecessary request roundtrips:
::: warning Deep updates not covered

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would that be enough to merge this PR?

Suggested change
::: warning Deep updates not covered
::: warning Deep updates not covered in Node.js

`@mandatory` validation is **not** applied to nested data in deep update operations. To enforce mandatory values in those cases, use the [`not null` constraint](../../cds/cdl#constraints) instead.
:::
Comment thread
mariayord marked this conversation as resolved.

```xml
<Annotations Target="Sue.Books/title">
<Annotation Term="Common.FieldControl" EnumMember="Common.FieldControlType/Mandatory"/>
</Annotations>
```
[Learn more about `@Fieldcontrol` annotation with `@mandatory`.](#mandatory-1){.learn-more}

<div id="mandatorywithexpressions"/>

Expand Down
Loading