This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision |
| b_i:required_with_owned_by_references [2023/03/09 03:35] – removed - external edit (Unknown date) 127.0.0.1 | b_i:required_with_owned_by_references [2023/05/10 01:23] (current) – sean |
|---|
| | {{tag>Known_Issues, Issue:References, Issue:Required, Issue:Business_Object, Issue:Rules}} |
| | <invisible> This is the template for INHERITED known issues pages - add a tag to Issue: to allow this to show on the tagged page</invisible> |
| | |
| | ==== Required With Owned By References ==== |
| | <grid> |
| | <col sm="1"><invisible> This is a spacer column</invisible></col> |
| | |
| | <col sm="5">===Problem/Limitation Description=== |
| | If two business objects are related through a parent/child relationship (see [[docs:2000_concepts:0200_basics:0400_reference_attributes|Reference Attributes]]) and the reference attribute to a child is defined as "Required" it is impossible to add a new child instance from a form of the parent instance using Add New button (see [[docs:8000_appendices:0200_known_issues:working_with_references_in_the_operation_mode]]) |
| | |
| | </col> |
| | |
| | <col sm="1"><invisible> This is a spacer column</invisible></col> |
| | |
| | <col sm="5">===Work Around=== |
| | Do not force "Required" flag for reference attributes or create child instance first and then add it to a parent using Add button. |
| | |
| | </col> |
| | </grid> |
| |