Last updated on MARCH 02, 2017
Applies to:Siebel CRM - Version 184.108.40.206  and later
Information in this document applies to any platform.
Checked for Relevance on 19-May-2014
Checked for Relevance on 11-Jan-2016
After an upgrade from Siebel 220.127.116.11 and Oracle 10g to Siebel 18.104.22.168 and Oracle 11g we experience a scripting issue when using the CountRecords() BC method with a customized BC ('Asset Mgmt - Asset - Header'). We have isolated how to reproduce this error: using a simple BS that execute a query followed by a count record Siebel build in a wrong way the count query totally different from the previous select statement. We have two different behaviors when using ExecuteQuery:
* ForwardOnly mode --> when executing the CountRecord() the exception of bad formatted query is displayed in the UI and the count is NOT performed,
* ForwardBackward mode --> when executing the CountRecord() the exception of bad formatted query is NOT displayed in the UI, the count is performed but the error 1 is logged.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms