Hi Community,
We have created a form through which we save Employee data and Employee's address through a separate section.
And we have 1-many relationship between Employee Entity and Address Entity, address being the child entity.
So we want to make entering an address row mandatory while creating an Employee through the Application Form.
How can this mandatory child entity relationship be enforced in the form?
Thanks
Hello,
To achieve that, you can create a validation rule that will allow creation of a record only if it already has a child. (any ChildEntities has (1=1) ).
This rule should be used only after the child creation part of the stepper (or you will be unable to create a record).
Here is some screenshot on how to proceed:
The validation rule of the parent entity:
In the stepper of the parent entity:
In the step for the creation of the parent, SKIP the rule, or you will be blocked before the opportunity of creating a child record.
In the step for the creation of the child, set this validation rule to WARN or BLOCK.
Then, when trying to create a parent without a child, an issue will be raised :
Hope this help,
Guillaume
Manoj. chinnaraj
Hi Community,
We have created a form through which we save Employee data and Employee's address through a separate section.
And we have 1-many relationship between Employee Entity and Address Entity, address being the child entity.
So we want to make entering an address row mandatory while creating an Employee through the Application Form.
How can this mandatory child entity relationship be enforced in the form?
Thanks
Hello,
To achieve that, you can create a validation rule that will allow creation of a record only if it already has a child. (any ChildEntities has (1=1) ).
This rule should be used only after the child creation part of the stepper (or you will be unable to create a record).
Here is some screenshot on how to proceed:
The validation rule of the parent entity:
In the stepper of the parent entity:
In the step for the creation of the parent, SKIP the rule, or you will be blocked before the opportunity of creating a child record.
In the step for the creation of the child, set this validation rule to WARN or BLOCK.
Then, when trying to create a parent without a child, an issue will be raised :
Hope this help,
Guillaume
Guillaume RIVOLLIER
Hello,
To achieve that, you can create a validation rule that will allow creation of a record only if it already has a child. (any ChildEntities has (1=1) ).
This rule should be used only after the child creation part of the stepper (or you will be unable to create a record).
Here is some screenshot on how to proceed:
The validation rule of the parent entity:
In the stepper of the parent entity:
In the step for the creation of the parent, SKIP the rule, or you will be blocked before the opportunity of creating a child record.
In the step for the creation of the child, set this validation rule to WARN or BLOCK.
Then, when trying to create a parent without a child, an issue will be raised :
Hope this help,
Guillaume
-
LOV label in Named Query
-
How we can set Dynamically changing Form field Description?
-
Is it possible to have a conditional survivorship rule based on a SemQL filter (akin to the filter on privileges)?
-
Where Do I View 2 Merged Records?
-
Show/hide an attribute in a form
-
Restrict access of attributes
-
Is it possible to manage visible/invisible value in List depend on user role??
-
Why am I unable to merge duplicates?
-
How are child records selected when parent records are manually merged?
-
Can the response from the API Call Response can be formatted differently in the JSON output?
See all 178 topics