My Oracle Support Banner

Disabled LOV Operation (Doc ID 2726260.1)

Last updated on NOVEMBER 12, 2020

Applies to:

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

Goal

We would like to understand the behavior of disabled LOV's. The understanding we have is a disabled LOV is just removed from being displayed to the user in the UI but is certainly accessible by other mediums. Eg, i have a LOV lookup value called Unknown This value is disabled as i dont want the users to use it and as its a mandatory field integration or data migration cannot bypass without passing a value when a record created , by passing a disabled value we are able to create a record successfully at the same type when a user opens the record he is forced to update a value.

when it comes to Importing records via Import Management or Integration, we would continue to want to create and update records with the UNKNOWN value.

We have tested the above scenario using Import Managament - Create and Update Works with the disabled value
We have tested the above scenario using REST API- create works with disabled value but fails on update.So we would like to understand why we are unable to update a record with a disable value via API.
 

Solution

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
Goal
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.