SetAttribute Not Working In After Changes Posted To Database
(Doc ID 2002722.1)
Last updated on OCTOBER 11, 2023
Applies to:
Oracle Fusion CRM Application Composer Cloud Service - Version 11.1.9.2.0 and laterInformation in this document applies to any platform.
Symptoms
setAttribute not working in After Changes Posted to Database
Written Groovy script trigger on After Chanegs Posted to a Database on a custom object. Trying to set the attribute of a field in the trigger, but this gives the error:
An application error occurred. See the incident log for more information.
ERROR
-----------------------
An Application Error Occurred . See the incident log for more details
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
The custom object is Customer Commercial Info, related to Accounts via 1:M relationship.
Click on any existing accounts:
Navigate to Commercial Info tab and click on New Button:
Click on Save and Close button for the record on SUI:
BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, Customer needs a business logic which can be enabled via this groovy script. Since this is erroring, he is not able to proceed and this is a show stopper for their project.
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 |