My Oracle Support Banner

BC Read Only Field User Property and disassociation of records (Doc ID 539398.1)

Last updated on MARCH 02, 2017

Applies to:

Siebel Tools - Version 8.0.0.1 [20408] and later
z*OBSOLETE: Microsoft Windows Server 2003
Product Release: V8 (Enterprise)
Version: 8.0.0.1 [20408] Auto
Database: Oracle 10.2.0.3
Application Server OS: Microsoft Windows 2003 Server SP1
Database Server OS: Novell SUSE Linux Enterprise 9.0
Checked for Relevance on 10-OCT-2011

This document was previously published as Siebel SR 38-3483221941.


Goal

We are intending to use the Business Component User Property "BC Read Only Field" to dynamically switch Records (e.g. Vehicles) to Read Only modus based on an attribute of the Vehicle Record.
This works fine in the business component - AutoVehicle.

Unfortunately setting the User Property also disables the Vehicles to be removed from Many to Many relationships (e.g. a Contact can have a M:M relation to Vehicles). For those Vehicles where the Read Only User Prop is TRUE, the relations in the Intersection Table can also not be deleted!

You can reproduce this also for Contact-Account relations by setting a BC User Property on Account. In that case you can not delete the relations in the "Contact Detail - Accounts View".
Is this expected behavior?
How could we make the record itself Read Only on a dynamic basis but be able to remove the relations?

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

This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.
My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.