SBL-DAT-00402: This operation is not available for read only field '%1'.

Applies to:

Siebel Tools - Version: 7.7.2 [18325] to 8.1.1 [21112] - Release: V7 to V8

Information in this document applies to any platform.
Error Message Area:Data Manager - DAT
Version:Siebel 7.7

Purpose

This document is intended to provide cause and corrective action information about Siebel Error Message SBL-DAT-00402: This operation is not available for read only field '%1'.

Scope

This document is informational and intended for any user.

SBL-DAT-00402: This operation is not available for read only field '%1'.

Explanation

1. A user or automated process such as a custom script or Workflow Process has attempted to update a field which is read-only. A field may be read-only for any of the following reasons:

a. It is a join field based on an explicit join.

b. It is part of a buscomp which has No Update = TRUE or referenced by a Link, Multi-value Link (MVL) or Multi-value Field (MVF) which has No Update = TRUE. For more information on the impact of the No Update property on these objects, refer to Siebel Bookshelf version 7.7 > Object Types Reference > Siebel Object Types for the object in question.

c. It has been designated as conditionally read-only using the Field Read Only Field buscomp user property, or the buscomp has been designated read-only using the BC Read Only Field or Parent Read Only Field user properties.

d. It is part of a MVF on a buscomp that is designated as read-only. If a script accesses the MVG buscomp using GetMVGBusComp and then tries to write to that buscomp, this error will occur because the MVG is considered to be read-only.

e. The field is read-only due to special class coding on the business component or applet.

f. The field is a system field such as Id, Created, or Created By. For more information on system fields, refer to Siebel Bookshelf version 7.7 > Configuring Siebel eBusiness Applications > Configuring Business Components > About System Fields.

NOTE: In Siebel applications prior to version 7.5.2.211, it was possible for a script to update a field even if it was designated as read-only. This was incorrect behavior and was fixed in Siebel applications version 7.5.2.211.

2. The error may occur when creating a new record in a pick applet if a pick map constraint has been set up using a joined field.

3. The error may occur on a MVG, referencing the read-only field SSA Primary Field, if the destination business component is read-only. This is because the Primary ID field is automatically updated through the system field SSA Primary Field, which belongs to the destination business component. Additionally, if this business component is read-only, the field is read-only as well and cannot be updated.

4. In Siebel applications version 7.5.3: Mobile clients attempted to download Literature items from the Briefings > My Briefings view.

Corrective Action

1. Identify the source of the action that led to the error, for example: user action, scripting, or workflow process. Determine if the field in question is intended to be read-only, and what configuration is used to make it read-only. If necessary, adjust your configuration to ensure that the field can be updated in this circumstance.
a. Join fields based on an explicit join are always read-only. If you need to update such a field through scripting, you will need to instantiate the business component that contains this field in its base table.
b. Check the No Update properties of the related buscomps, applets, links, and MVLs, and the Read Only property of related MVFs. Make any necessary changes to make it possible for the user, script, or other automated process to update the field. For example, you can make a field read-only on the applet level by setting the applet No Update property or the control or list column Read Only property, but make the field modifiable at the buscomp level so that a script or workflow process can update the field.
c. Check if there are Business Component User Properties defined for Field Read Only Field, BC Read Only Field, or Parent Read Only Field. These user properties will dynamically decide whether a field or record is read only, based on the value in another field. For details, refer to Siebel Bookshelf version 7.7 > Configuring Siebel eBusiness Applications > Configuring Business Components > Configuring Data-Driven Read-Only Behavior. Make sure the field that determines the read-only status has been set up according to the exact business needs.
d. If you are trying to set a field through scripting, and you have used the GetMVGBusComp method to access the buscomp, check if the parent buscomp is set to read-only through one of the mechanisms described above. If necessary, instantiate the buscomp using an alternative method, such as GetBusObject and GetBusComp, so that the buscomp will allow updates in that context.
e. Check the buscomp and applet to see if they use a special class. If the special class object is part of the standard Siebel application, do not change the class property; find an alternative implementation. If the special class object is a custom object, consider whether it needs the special class or if it should use a standard class. For more information, refer to Siebel Bookshelf version 7.7 > Configuring Siebel eBusiness Applications > Overview of Configuring Siebel Applications > About Configuring Siebel Applications > About Copying Objects, and Siebel Bookshelf version 7.5.3 > Configuration Guidelines > Creating and Modifying Objects > Creating Specialized Objects > Cloning Specialized Objects.
f. Make sure you are not trying to set a system field: Id, Created, Created By, Updated, or Updated By.

2. If the error occurs when clicking the New button in a pick applet, check to see if the pick map is constrained. If necessary, adjust the configuration so that the constraint does not rely on a joined field. For details, refer to Siebel Bookshelf version 7.7 > Configuring Siebel eBusiness Applications > Configuring Picklists and Pick Applets > About Dynamic Picklists > Constraining Dynamic Picklists.

3. If the error occurs on a MVG field, referencing the read-only field SSA Primary Field, make sure the destination business component of the corresponding MVL is not read-only. For details, refer to Siebel Bookshelf version 7.7 > Configuring Siebel eBusiness Applications > Configuring Links > Configuring the Primary ID Field.

4. When creating literature items, set the Request File option in the Document Administration > Literature view. This will help bring the files to the mobile client.

Applies to:

Siebel CRM - Version: 8.1.1 SIA [21111] and later   [Release: V8 and later ]
Information in this document applies to any platform.

Goal

Error message SBL-DAT-00402 was observed after applying the workaround for Change Request Bug 12-1RSSIAT, as documented in Doc ID Note 762140.1: End of file error for Revise Quotes.
-> Workaround implemented:
Add two actions to signal ReviseCopyQuote, one to capture the id of the original quote and another to repair the primary sales rep of the new quote.
Objects, details and implementation steps are attached in objects.zip
-> After importing the objects given in the SR and verifying the changes, the following error message is observed:
This operation is not available for read only field 'SSA Primary Field'.(SBL-DAT-00402)

=> Questions:

(1) Is this related to the business service script that was provided in the SR specified above?

(2) In which version of Siebel is Change Request Bug 12-1RSSIAT implemented?

Solution

Ad (1)
The workaround to Change Request # 12-1RSSIAT has been tested in Siebel v8.1.1 [21112], and it worked fine.
However, another issue was found in this version:
The workaround provided with CR# 12-1RSSIAT does not solve the issue when revising a quote in the.Service Requests > Quotes view. A new Change Request Bug 12-1X65TFH has been created for this behaviour.
So the error message may occur for one of the following reasons:
a) The user revised the quote in a different screen from the Quotes screen.
b) There are customizations on the Quote business component that make the revision read-only.

In this case it was found to have occurred because of custom scripting.


Ad (2)
Change Request # 12-1RSSIAT has not been implemented yet. Currently it is targetted to a future version of the Siebel application.

References

BUG:12-1RSSIAT - REVISE QUOTE ERRORS OUT IN CASE CURRENT USER NOT PRIMARY ON TEAM
NOTE:762140.1 - End of file error for Revise Quotes

Applies to:

Siebel Tools - Version: 7.7.2.7 SIA [18376] and later   [Release: V7 and later ]
Information in this document applies to any platform.

Symptoms

After patched environment from 7.7.2.7 to 7.7.2.11,  the below error message occurs when adding an Address to a Contact:

ERROR
-----------------------
This operation is not available for read only field 'NOVA Primary Address Id' (SBL-DAT-00402).


STEPS
-----------------------
1) Goto Contacts Screen
2) Click Address MVG field to open Address MVG applet
3) Click New button on the MVG applet
4) On the popup applet, enter the address info
5) Cick Ok on the popup applet to save the address info, then the error message pops up. However, the address is saved successfully.

Changes

Environment is upgraded from 7.7.2.7 to 7.7.2.11

Cause

The behavior is reproduced in sample database, and CR 12-1S5B33Z (SBL-DAT-00402: This operation is not available for read only field) was logged to report this behavior.

Config Steps:
1) Copy "Position Join" Join and name it as NOVA S_POSTN_CON, delete the "Position Id" Join Constraint

2) Create a new field the below value:
Name = NOVA Primary Address Id
Join = NOVA S_POSTN_CON
Column = PR_ADDR_ID
Force Active = True
Link Specification = True

3) Copy the "Pharma Address" mvl , and change the new mvl with the below vlaues:
Name = NOVA Pharma Address
Primary ID Field = NOVA Primary Address Id

4) Copy "Street Address" mvf, and change the new mvf with the below values:
Name = NOVA Street Address - All
Multivalue Link = NOVA Pharma Address
Force Active = True

5) Set Force Active to True for the below fields
"Address Name"
"Street Address"

Steps to Repro:
1) Goto Contacts Screen
2) Click Address MVG field to open Address MVG applet
3) Click New button on the MVG applet
4) On the popup applet, enter the address info
5) Click Ok on the popup applet to save the address info, then the error message pops up "This operation is not available for read only field 'NOVA Primary Address Id' (SBL-DAT-00402).
However, the address is saved successfully.

Solution

To fix the error message "This operation is not available for read only field 'NOVA Primary Address Id' (SBL-DAT-00402)", please follow the below steps:
1) Login to Siebel Tools,
2) Query for the Contact buscomp
3) Query for the "Address Name" field
4) Change the "Force Active" property to False for the "Address Name" field
5) Compile the changes.

References

BUG:12-1S5B33Z - SBL-DAT-00402: THIS OPERATION IS NOT AVAILABLE FOR READ ONLY FIELD

Applies to:

Siebel Tools
z*OBSOLETE: Microsoft Windows Server 2003
Product Release: V8 (Enterprise)
Version: 8.0 [20405]
Database: Microsoft SQL Server 2000 SP3
Application Server OS: Microsoft Windows 2003 Server SP1
Database Server OS: Microsoft Windows 2003 Server SP1

This document was previously published as Siebel SR 38-3420128083.
Checked for relevance on 19-11-2010

Symptoms

SBL-DAT-00402

Hello,

I am putting this SR at a priority 2 because I cannot proceed with development without this issue being resolved.

I have recently completed an upgrade from Siebel 7.8 to 8.0.0.1. The issue I have is when I try to create a new order record I get the following error:

"This operation is not available for ead only field 'Type' (SBL-DAT-00402)

I get this error both using a dedicated web client, as well as the thin client against the server database. In both cases, I am using a configured SRF.

I do NOT get this error using the OOTB Siebel 8 SRF on a dedicated client against the server db.

I have attached a log file which includes the aforementioned error. It seems related to a completely different BC (ISS Context VOD Query BusComp). The field 'Type' does not exist either in the configured Order Entry - Orders BC nor the VOD BC. I am not sure why this BC is called in the first place, and that too, in the configured SRF.

Can you please help me identify the cause of the error so I can create an Order record?

Thanks,

Solution

Message 1

For the benefit of other users:-

Customer have recently completed an upgrade from Siebel 7.8 to 8.0.0.1. The issue is when they try to create a new order record , get the following error:

This operation is not available for read only field 'Type'.(SBL-DAT-00402)

In the customer’s configuration, they have removed the the pickist property for the the Field >Order Type and that was the cause of the error, so suggested the customer to change the folowing:-

In the BC "Order Entry - Orders" > field,"Order Type' , please provide a value for the picklist property.
Compile the BC.

We could reproduce the error by making the following changes in 8.0 Appication.

1) In Tools, goto BC>Order Entry - Orders
2)Field >Order Type>Remove the pickist property
3)Compile the BC
4)In the Sales application, goto the Sales Orders screen
5) Add new order form Order home page
Error Message "This operation is not available for read only field 'Type'.(SBL-DAT-00402) "

[cont..]

Message 2

We've tested the same configuration in different HOR versions and this issue is reproducible only in 7.8 HOR and 8.0 HOR env .and this is NOT reproducible in 7.5 HOR and 7.7 HOR env.

Whie investigating this issue it is confirmed that when the specialized class on the BC 'Order Entry - Orders' was changed from '"CSSBCOrderMgmtOrder"' to the "CSSBusComp" for test purpose , the error is no longer occuring with the same configuration.

The class property of the BC "Order Entry - Orders" is "CSSBCOrder" in 7.5 and 7.7. and is "CSSBCOrderMgmtOrder" in 7.8 and 8.0.

We've logged a new CR #12-1KNI8OF "This operation is not available for read only field 'Type' after removing the pickist for Order Type" to address this issue.

Thank you,
Siebel Technical Support