Add a Classification Against An Account

(Doc ID 2149165.1)

Last updated on JULY 20, 2016

Applies to:

Oracle Fusion Sales Cloud Service - Version to [Release 1.0]
Information in this document applies to any platform.


On : version, Accounts, Contacts, Households

Groovy not working as expected

There is some script that puts a classification against an account which is working fine.
Recently updated this to include a second classification, however for some reason it is setting both classifications as primary and when the territory assignment happens, it doesn't fully work (only assigns one or the other territory).

Also tried removing the line " CodeName.setAttribute('PrimaryFlag', 'N') " but it still adds it as a primary classification. Why this would be and how can prevent this from happening?


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms