Applies to:Siebel Tools - Version: 126.96.36.199 SIA 
Information in this document applies to any platform.
Checked for relevance on 25-Nov-2010
Customer implemented the DisableSearch User Property for many fields to prevent users from searching on fields. The error message for this validation displays the Business Component Field Name and not the UI Label Name. This has caused confusion for their users as the BC Field Names do not always match the UI Label Name.
o The loss of functionality
None. The DisableSearch field user property works because an error message displays when a user tries to query on a field that has DisableSearch user property set to TRUE
o Environment< Siebel 188.8.131.52 sia >
o Include specific error messages (error number with syntax)
'Searching has been disabled on the '
o What IS working
The functionality of the field user property works fine, it's just the error message create some confusion for the users because the field display name is not always the same as the field name at the bc level
o What is the expected or acceptable result?
The error message uses the display name at the applet level instead of the field name at the bc level.
The issue was reproduced against the sample db and vanilla srf file with the following steps:
1. In Siebel Tools, query for Account BC
2. Query for the Account Type Code field (The display name for this field is called Account Class at the ISS Account List applet)
3. Add a field user property
4. Recompile the srf file
5. Log into Siebel Client application
6. Go to the Accounts screen > Account List view
7. Query on the Account Class column with wildcard
8. An error shows:
'Searching has been disabled on the 'Account Type Code' field. Please refine your search to exclude the 'Account Type Code' field (SBL-DAT-00818)
The above error message is by designed. To avoid the confusion, Change Request 3-E4X8DD has been logged to address this product enhancement request. In the CR, it has been requested to use the Display Name instead of Field name in the DisableSearch error message.
We have done some research on the issue and reproduce the same behavior. It has been confirmed that the error message is expected:
'Searching has been disabled on the '
The error message is generated from the C++ code. Thus, we cannot change the error message to use the field Display name (label name). However, Change Request 3-E4X8DD has been logged to address this product enhancement request. One possible way to workaround the issue is to set the Display Name for the field at the applet level to match the Field Name at the BC level.
Applies to:Product Release: V7 (Enterprise)
Version: 184.108.40.206 
Database: Oracle 220.127.116.11
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-3323291241.
Due to performance consideration, I intend the disasble the Query for a Field that's shown in a
In Business Component: Action, I have configured the function 'DisableSearch' in Field User Prop. Upon testing it, the query is disable for the first time search - pop up message: 'Searching has been disabled on the '<Field Name>' field. Please refine your search to exclude the '<Field Name>' field. However, when user click 'Go' again (without undo query), this field can be queried.
Steps to replicate:
1) Navigate to the List Applet
2) Click 'Query' button
3) Enter Search Spec in Field
4) Click 'Go' (error message will pop)
5) Click 'OK' on pop up window
6) Click 'Go' again.
Message 1For the benefit of other users,
I have reproduced reported issue by configuring the following:
In Action BC > Description Field, configure DisableSearch = TRUE user property.
In the UI, Click Query and enter the following different search spec:
Click Go button and error message appears "Searching has been disabled on the 'Description' field. Please refine your search to exclude the 'Description' field. (SBL-DAT-00818).
Click OK button on the popup message box.
Click Go button again.
For search string 1), the error message appears again.
For search string 2), the query is executed.
According to Siebel Developer's Reference > User Properties > DisableSearch:
If its value is TRUE, wildcard searching on the field is disabled, but exact match searching is allowed.
However error message should not appear for search string 2) if the query is allowed.
Change Request 12-1IZXMXK has been logged to address this defect.
According to Service Request #: 38-182239351 in supportweb:
There is currently no property you can set at the field level to determine if a field can be queried or not. Enhancement Request #12-30U78Y has been logged requesting for the ability to refrain from querying on certain fields.
The only workaround to prevent the user from querying on certain fields is to add script in the PreQuery event.
Post a Comment