Skip to content

clarify @mandatory is not validated in deep updates #2585

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
mariayord wants to merge 7 commits into
base: main
Choose a base branch
from
Open

clarify @mandatory is not validated in deep updates #2585

Changes from all commits
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
73b96c8
clarify @mandatory is not validated in deep updates, fix wrong info r…
mariayord May 20, 2026
8b50ac5
removed section, as it is mentioned already in Field Control below
mariayord May 20, 2026
fa73d2d
Update guides/services/constraints.md
mariayord Jun 9, 2026
fa62f90
Merge branch 'main' into mandatory-deep-update
renejeglinsky Jun 23, 2026
79b9a23
Update constraints.md
mariayord Sep 4, 2026
d594707
Update guides/services/constraints.md
renejeglinsky Sep 7, 2026
eef34b2
Apply suggestion from @renejeglinsky
renejeglinsky Sep 7, 2026
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
14 changes: 8 additions & 6 deletions guides/services/constraints.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -368,13 +368,15 @@ 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:
#### ... in Compositions
For insert/update, a mandatory value is **not** enforced when the property is missing from the request.
However, an explicitly provided `null/''` value is validated and rejected. This rule applies to compositions and cascading compositions. To enforce mandatory values, use the [`not null` constraint](../../cds/cdl#constraints) instead.

```xml
<Annotations Target="Sue.Books/title">
<Annotation Term="Common.FieldControl" EnumMember="Common.FieldControlType/Mandatory"/>
</Annotations>
```
#### ... in Associations

@johannes-vogel johannes-vogel Sep 7, 2026 •
edited
Loading

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.

I don't think we need to repeat the section for associations. In associations, only the foreign key is respected. all other elements are not validated, it's not in particular specific for mandatory.

@renejeglinsky renejeglinsky Sep 8, 2026

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.

In a previous version I had the impression that there was a notable change for associations:
image

If we'd remove the whole section about associations we'd loose the information about the not null constraint. Or should we move that somewhere else?

@renejeglinsky renejeglinsky Sep 8, 2026

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.

Should this sentence, for example, be moved to the general section?


For insert/update, a mandatory value is **not** enforced when the property is missing from the request. Even an explicitly provided `null/''` value is accepted. To enforce mandatory values, use the [`not null` constraint](../../cds/cdl#constraints) instead.
Comment thread
renejeglinsky marked this conversation as resolved.

[Learn more about `@Fieldcontrol` annotation with `@mandatory`.](#mandatory-1){.learn-more}

<div id="mandatorywithexpressions"/>

Expand Down
Loading