Field Validation Is Triggering Even If The Field Is Not Modified
(Doc ID 2925572.1)
Last updated on AUGUST 18, 2023
Applies to:
Oracle Fusion CX Sales Cloud Service - Version 11.13.22.10.0 and laterInformation in this document applies to any platform.
Symptoms
On : 11.13.22.10.0 version, Partner Management
ACTUAL BEHAVIOR
---------------
Setup:
A custom object A was created, under Partner.
A M:M relationship between custom object and standard Partner object.
Create multi-select FCL field B both in custom object A and Partner Object.
Field validations were created for the FCL fields in order to restrict the update of those fields in the Partner Object.
A scheduled Process was setup in order to update the fields based on the custom objects A added under Partner Object.
When the user is opening a Partner record and the process just ran, the validation for the field B is firing even if the user does not change the B field.
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |