My Oracle Support Banner

[19C OCT]: Trigger Groovy On Lead Associated Account Field (Doc ID 2590793.1)

Last updated on SEPTEMBER 20, 2019

Applies to:

Oracle Fusion Sales Cloud Service - Version 11.1.11.1.0 and later
Information in this document applies to any platform.

Symptoms

On : 11.1.11.1.0 version, Sales, Sales Catalog

ACTUAL BEHAVIOR
---------------
Field Trigger Groovy on DCL does not work correctly

Trigger field is associated account on Sales Lead -> triggers only for change empty -> value. Not triggered when removed or updated.

when you remove the Account -> Field trigger is triggered (before you save)
when you add an Account -> Field trigger is not triggered
when you add an Account and click on save -> Field trigger is triggered

Tracked via id 28422445 - SIMPLE FIELD TRIGGER ON ACCOUNT FIELD (SVP COMPONENT) IS NOT WORKING
Issue occurs when the object validation is defined on top of the DCL field


Until the fix is available, we would suggest not to use field triggers based on DCL fields which are drill down enabled.
Instead you can try a before insert/update trigger and the intended change would be reflected on clicking Save.
 

EXPECTED BEHAVIOR
-----------------------
validation must be triggered

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
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.