Search This Blog

SBL-DAT-00479: %2 doesn't support operator '%1'

Applies to:

Siebel Tools Complete, SPE - Version: SIA [20416] and later   [Release: V8 and later ]
Information in this document applies to any platform.
""Checked for Relevance on 02-Sep-2010""


The customer defined the 2 following user properties on BC 'FS Repair':
- - -
Name: On Field Update Invoke 1
Value: "Sub-Status", "FS Repair", "Create Notification", "[Status] = LookupValue('FS_REPAIR_STATUS','Returned from ASC') AND [Sub-Status] = LookupValue('FS_REPAIR_STATUS','Validated')"
- - -
Name: Named Method 5
Value: "Create Notification", "INVOKESVC", "FS Repair", "Workflow Process Manager", "RunProcess", "'ProcessName'", "O2 Repair - Create Notification", "'Repair Id'", "[Id]"
- - -

When they changed the value of the Sub-Status field on the FS Repair applet so to trigger the user properties, they received the following error:
- - -
CSSString doesn't support operator '-'(SBL-DAT-00479)
- - -


The Value for the Named Method 5 user property has 9 quoted parameters. The 7th parameter contains the name of the workflow process to invoke.

The name is:  O2 Repair - Create Notification

The error is due to the hyphen character (-) in the workflow process name.


The solution is to enclose the name with single quotes, 'O2 Repair - Create Notification', namely use the syntax below for the 7th parameter:

"'O2 Repair - Create Notification'"

instead of:

"O2 Repair - Create Notification"

NOTE: You can also use quotes instead of single quotes but in this case enclose the name with 2 pairs of quotes, ""O2 Repair - Create Notification"" namely use the syntax below:

"""O2 Repair - Create Notification"""

The Named Method n user property is documented in the Bookshelf:

Siebel Developer's Reference
User Properties
Business Component User Properties
Named Method n (Business Component)

Bug 12-1SMKV4R has been logged asking to clarify the syntax/rule for this user property and provide examples.



Applies to:

Siebel Tools - Version: SIA [19221] and later   [Release: V7 and later ]
IBM AIX on POWER Systems (64-bit)
AIX5L Based Systems (64-bit)
Product Release: V7 (Professional)
Version: [19221] CHT
Database: Oracle
Application Server OS: IBM AIX 5L 5.2
Database Server OS: IBM AIX 5L 5.2

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


Hi there,

We configured a MLOV field and assigned it to a list applet. When user clicks the list column, it displays the below popup error message

CSString doesn't support operator '-'(SBL-DAT-00479)

I checked the supportweb with the above Siebel error code & CSSString but can't find anything related to this sorting problem.

We also have defined other MLOV but didn't encounter this error.

Attached is an excel file contains the
1. LOV_TYPE setup
2. the LOV setup
3. picklist setup
4. table column setup
5. the BC field and its pickmap setup

Please advise workaround.   Thank you.


Using of '-' in MLOV or Join Constraint.


This is reproduced internally and are logged as Bug 12-1J5G0OC and Bug 12-1OMWHH5.


Message 1

For the benefits of other users:

Customer configured a MLOV field and assigned it to a list applet. When user clicks the list column to sort it, the following error message was obtained.

CSString doesn't support operator '-'(SBL-DAT-00479)


This error message occurred only when a MLOV is based on a LOV_TYPE that contains hyphen character, '- '. However, the error message did not occur when a LOV is based on a LOV_TYPE that contains '-'.

Bug 12-1J5G0OC has been logged regarding this behaviour.

In the meantime, please try not to use LOV_TYPE that contains '-' for MLOV.

The same error SBL-DAT-00479 is encountered if dash or '-' is used in join constraint. Bug 12-1OMWHH5 is also logged to address "Error SBL-DAT-00479 is thrown when configuring a join constraint containing a value with a dash"

Please log a Service Request if there is any doubts or clarifications required regarding this issue.

Siebel Technical Support.



Applies to:

Product Release: V7 (Professional)
Version: [18372]
Database: Oracle
Application Server OS: Microsoft Windows 2003 Server SP1
Database Server OS: HP-UX 10.0

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


We are doing some changes to our CTI configuration (with Genesys). Under Administration - Communications > All Configurations > Event Handlers we're configuring the following Event Handler Parameter under a specific Event Handler (VFCCInboundCallRingingManualAnswer):

Name: FilterSpec
Value: {ThisDN} LIKE '213?' OR {ThisDN} LIKE '214?' OR {ThisDN} LIKE '215?'

The problem is that when invoking this particular event handler we're getting the following error in the SComm log:

ERROR:Failed on evaulating filter spec({ThisDN} LIKE '214?' OR {ThisDN} LIKE '215?'), err=22150, msg=CSSNumber doesn't support operator 'LIKE'(SBL-DAT-00479)

If we use the following FilterSpec we don't get an error and it works as it is supposed:

Value: {ThisDN} = '2142'

But our purpose is to use wildcards in the number. For that we used the LIKE operator but without success.


Message 1

* For the benefit of other users *
As per Siebel Communications Server Administration Guide, version 7.7 > Configuring Events and Commands > Event Handlers > section Event Handler Parameters >
Table 13. Event Handler Parameters, you should be able to use simple and complex queries:
Event data-field filter that supports simple or complex queries.

Filter results are evaluated using a compound predicate that can include standard query operators to determine if the event handler matches the event.

FilterSpec queries use standard comparison operators, including:


The following behavior has been noted:

When FilterSpec is set as follows, then it works:

FilterSpec={OtherDN}=9002 OR {OtherDN}=9003 OR {OtherDN}=9004

When the below operators are used, FilterSpec doesn’t work:

FilterSpec = '{OtherDN}=9002' OR '{OtherDN}=9003'
filterSpec = {OtherDN}=900* OR {OtherDN}=900* OR {OtherDN}=900*
FilterSpec = {OtherDN} LIKE '9004'
FilterSpec = {OtherDN}='900*'

To address this, new Change Request 12-1IP5R2K has been logged.

Oracle Support
Keywords: “FilterSpec”, “FilterSpec and CTI”, “SBL-DAT-00479”

Applies to:

Siebel Universal Customer Master - Version: [19044] and later   [Release: V7 and later ]
IBM AIX on POWER Systems (64-bit)
Product Release: V7 (Enterprise)
Version: [19044]
Database: IBM DB2/390 V7
Application Server OS: IBM AIX 5L 5.2
Database Server OS: IBM zOS

This document was previously published as Siebel SR 38-2558448411.
***Checked for relevance on 27-OCT-2010***


When executing the UCM Account Batch Data Management Workflow, the following error was observed:

Error invoking service 'UCM Batch Manager', method 'HandleMatchCase' at step 'Process AutoMatch'.(SBL-BPR-00162)
Method 'FieldValue' of business component 'Account' (integration component 'Account') for record with search specification '[Party UId] = "34AB7C0B-45AA-44d8-9E72-DF299E588ECA"' returned the following error:"The query expression on field 'Assessment Value' is not valid. Please revise and try again.(SBL-DAT-00399)"(SBL-EAI-04451)


Through research and tests, it was found that the reported error was caused by custom integration component field ‘Assessment Star Value’ in Account integration component within CIFAccount integration object. The reason why the reported error occurs was that the Assessment Star Value is a calculated field and the Calculated Value is [Assessment Value]/25. Here, the data type of ‘Assessment Value’ field is DTYPE_TEXT so that it is not allowed to divide string data with numeric value. Then the following errors are caused:

ObjMgrMiscLog Warning 2 0 2005-10-06 15:45:44 (ssdatum.cpp (754)) SBL-DAT-00479: CSSString doesn't support operator '/'

ObjMgrQueryLog Warning 2 0 2005-10-06 15:45:44 (query.cpp (6877)) SBL-DAT-00399: The query expression on field 'Assessment Value' is not valid. Please revise and try again.


BUG: 12-16EHBFU has been logged to address this incorrect Calculated Value in UCM standard application.

A workaround is to change the Calculated Value for the Assessment Star Value field on Account business component as follows:

From: [Assessment Value]/25
To: 1*[Assessment Value]/25

It is because when a Calculated Value statement references more than one field value and constant, and each field and constant has different data types, the order of the data types can have an effect on the calculation. In other words, the calculated value is left-centric.



Applies to:

Product Release: V7 (Enterprise)
Version: [16066] Com/Med
Database: Oracle
Application Server OS: Microsoft Windows 2000 Server
Database Server OS: HP-UX 11i

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



For an Oracle 11i upgrade we recently end dated all our products and our price list, and loaded all new ones. Since this data change we get the following error whenever trying to access the shopping cart in eSales:

We detected an Error which may have occurred for one or more of the following reasons:

%2 doesn't support operator '%1'

I've run it in the thick client and it doesn't give any other information either. Please help this needs to be resolved by tomorrow 6am. Call me on my cell at ####. Thanks,


Message 1

For the benefit of other users:

The database upgrade and the change to new products and price lists were unrelated to the error.

The Object Manager (= OM) logs contained an additional error: CSSString doesn't support operator 'AND'. A SupportWeb search for 'CSSString' lets find the posting 'SR: Siebel Query Language' (SR 38-662392551). The main information from there is that the CSSString errror is produced by the expression interpreter, which is used for example when doing queries.

Further analysis of the OM logs showed a Named Search 'Content Targeting Named Search' on the data object of the business component 'Quote', where the query expression was corrupt. It contained snippets of HTML pages including all the tags, these snippets are bound together with AND operators.

When the expression interpreter gets this query, it implicitely switches the datatype to text, because the expression starts with text. Then it sees that a couple of text strings is connected with AND. Since AND operator is valid on booloean data only the error message is issued.

Based on the text in the corrupt query customer found out that an incorrect personalization rule caused this query. After removing the personalization rule the shopping cart could be accesses without problems.

Siebel Technical Support

No comments:

Post a Comment