Applies to:
Siebel Tools - Version: 7.7.1 [18306]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-00359: The value '%1' cannot be converted to a date time value.
Scope
This document is informational and intended for any user.
SBL-DAT-00359: The value '%1' cannot be converted to a date time value.
Explanation
Below are some reported causes for this error:1) When calling the SetFormattedFieldValue method this error might be displayed in the Siebel Dedicated Web client. The difference between the Siebel Dedicated Web clients and Siebel Web clients is discussed in the Siebel Bookshelf version 7.7 > Applications Administration Guide > Initial Setup > Setting Up Locales - where it states, "Whereas the Siebel Web Clients use the locale settings specified in the Locale Administration view, the Siebel Mobile Web Client and the Siebel Dedicated Web Client use the locale settings defined in the client operating system's regional settings."
2) An error is displayed when a business component field specifies a Pre Default Value with a timestamp that is not encapsulated in double quotes.
3) When querying on date fields in the Siebel UI using the same date format specified by the application locale, but the date separator is incorrect, then this causes an error. For more information on the Date Separator, please refer to Siebel Bookshelf version 7.7 > Applications Administration Guide > Initial Setup > Setting Up Locales.
4) When using the Find drop-down list in pick applets, where a field is selected based on date and time format, and then an error is displayed. For example, Account Entry Applet - Price List pick field - and then searching on Start Date. Sometimes error SBL-DAT-00403 is displayed advising the user to encapsulate the search criteria in quotations; however the above error message still appears.
5) Querying on Find fields in the Siebel Search Center that are based on dates can cause errors if the query string does not match the application default date format.
6) An error might be generated when importing an XML formatted message into the Siebel application via Integration Objects, especially when the IO Field is set to DTYPE_TEXT and the value in the XML message is encapsulated in double quotes.
7) The EAI Siebel Adapter does not perform date or time validation rather this is done at the user interface layer and therefore if the format is incorrect or contains invalid characters no error appears. In some cases, for example where the year is specified as 2 digits as opposed to 4 digits, then this type of validation is handled by the Siebel object manager as described in Siebel Bookshelf version 7.7 > Siebel eScript Language Reference > Siebel eScript Language Overview > Siebel eScript Programming Guidelines (Use four-digit years in dates).
8) A workflow process might throw an error if it specifies the Match Date property on Update operations, for example,
Field Name: Suspended Date
Type: Expression
Value: [&Match Date] + 30
9) An error might occur when creating a Workflow Policy Condition that involves a comparison between two workflow policy columns based on a date data type.
10) A campaign load might fail if the format of date fields is incorrect.
Corrective Action
Below are the corrective actions to try for the reported causes:
1) It is recommended to convert the date into the respective format specified by the regional settings, for example "dd.mm.yyyy", and then call the SetFieldValue with the converted value as described in this Bulletin <Doc: 475872.1>.
How to work with date and numeric fields in Siebel Visual Basic (SVB) (Doc ID 475872.1)
For more information on the script syntax, please refer to Siebel Bookshelf version 7.7 > Siebel Object Interfaces Reference > Interfaces Reference > Business Component Methods > SetFormattedFieldValue Method.
Change Request 12-I54UKV was logged to address this product defect, which has been fixed in Siebel 7.7.
2) The Pre Default Value property should be specified using the format "hh:mm:ss" and encapsulated in double quotes. The field itself should be based on the DTYPE_TIME Date Type. Please refer to this bulletin <Doc: 477773.1> for more information on this matter.
Predefault and Postdefault Values for Fields of Type Date, Date Time, and UTC Date Time (Doc ID 477773.1)
3) Ensure that the Date Separator specified under Application Administration > Locale - reflects the same separator specified in the Short Date Format.
4) As a workaround when performing a query in a pick applet on a date field, use the Query button as opposed to using the Find drop-down list. Change Request 12-PDZ7T2 was logged to address this product defect.
5) Scripting could be used as an alternative in order to validate the search strings entered in the Find fields. Change Request 12-L5URHJ was logged to address this product defect.
6) Either, a) specify the IO Field as DTYPE_DATETIME (no double quotes needed in the XML) using format “YYYY/MM/DD HH:MM:SS” or specify “HH:MM:SS” (without quotes) as the XML element value. In addition, the Length property of the integration component field should be removed, because when an integration object and integration component is generated, the Length property of the integration component field with DTYPE_DATETIME as Type is set to null by default or b) change the Data Type of the integration component field to DTYPE_TEXT and specify the value without quotes. Ensure that the Length property is set correctly, for example from 7 to 8 on integration component field and the BC field.
7) Ensure that date values are passed using the correct format to the EAI Siebel Adaptor. Change Request 12-MDI6LC has been logged to address a product defect related to how the same data validation should be present in the EAI Siebel Adaptor as in the Siebel UI.
8) Ensure that the process property called Match Date has the Data Type set to Date as opposed to String. For more information, please refer to Siebel Bookshelf version 7.7 > Siebel Business Process Designer Administration Guide > For Developers: Workflow Process Steps > About Process Properties > Defining Process Properties.
9) Please refer to this document <Doc: 475967.1> where it states that the comparison of two columns in a workflow policy condition is currently not possible in Siebel 7.
Can a Workflow Manager Policy Have a Condition That Compares Two Columns to Each Other? (Doc ID 475967.1)
Change Request Bug: 12-K9BP8N was logged to address this product enhancement request. Instead use a workflow process to do this comparison.
10) Under Marketing Administration> External Data Mapping > Tables - the field expression should be amended to return a string using the format "mm/dd/yyyy hh:mm:ss".
Applies to:
Siebel Tools - Version: 8.0.0.1 SIA [20408] - Release: V8Information in this document applies to any platform.
Symptoms
Error SBL-DAT-00359 was observed and the behavior was intermittent and is not observed once the server was restarted.
Behavior was observed only on customer test environment and works fine on development environment with same srf.
Cause
This line of script was causing the error with Clib object.
var TimeBuf;
var FormattedDateMs = FormattedDate.getTime();
Clib.strftime(TimeBuf, “%c”, FormattedDateMs);
Solution
Workaround used was creating a custom function that used .getMinutes, .getHours..etc and concatenated these items together to form the date string as this.SetFieldValue("UPS Customer Time", sStringVariable");
<<CR#12-1PE9QS4>>was logged as product defect that there is problem with Clib and Time buffer parameter.
Applies to:
Siebel Tools - Version: 7.8.2 [19213]Information in this document applies to any platform.
Symptoms
For Service Request customer has modified applets to display the Day of the Week for field types DTYPE_UTC_DATETIME.Customer set the Display Format for Applet Control as ‘DDDD Date Time’.
However, when customer tries to query on this field they got error "The value 'Tuesday 7/29/2008 5:14:08 PM' cannot be converted to a date time value. (SBL-DAT-00359)".
Cause
It seems that “Display Format” is not available for DTYPE_UTCDATETIME and Enhancement Request Bug 12-1L6MQ19 has been logged to have Display Format for DTYPE_UTCDATETIME.However, the same behavior is happening for a field of type DTYPE_DATETIME for which the display Format is available.
Product Defect Bug 12-1PILZ6F - Error SBL-DAT-00359 is generated when querying on control with Display Format as DDDD Date Time has been created.
Solution
The issue has been replicated internally and Bug 12-1PILZ6F - Error SBL-DAT-00359 is generated when querying on control with Display Format as DDDD Date Time has been created.
The only way to avoid the error would be to remove the Display Format set for this field.
In order to have the weekday of the Service Creation you can do the following:
1. Create a clone of the control and set the Display Format as DDDD for this control, so that you can see the Weekday of Service Request creation.
2. Use the other field for query.
Oracle Customer Support
Note: Bug 12-1PILZ6F - Error SBL-DAT-00359 is generated when querying on control with Display Format as DDDD Date Time has been created has been currently declined as Risks Exceed Benefits.
References
BUG:12-1PILZ6F - ERROR SBL-DAT-00359 IS GENERATED WHEN QUERYING ON CONTROL WITH DISPLAY FORMAT AS DDDD DATE TIMEApplies to:
Error Message Area:Data Manager - DATVersion:Siebel 7.5.3
Purpose
This document is intended to provide cause and corrective action information about Siebel Error Message SBL-DAT-00359: The value '%1' cannot be converted to a date time value.
Scope
This document is informational and intended for any user.
SBL-DAT-00359: The value '%1' cannot be converted to a date time value.
Explanation
Below are some reported causes for this error:1) When calling the SetFormattedFieldValue method this error might be displayed in the Siebel Dedicated Web client. The difference between the Siebel Dedicated Web clients and Siebel Web clients is discussed in the Siebel Bookshelf version 7.7 > Applications Administration Guide > Initial Setup > Setting Up Locales - where it states, "Whereas the Siebel Web Clients use the locale settings specified in the Locale Administration view, the Siebel Mobile Web Client and the Siebel Dedicated Web Client use the locale settings defined in the client operating system's regional settings."
2) An error is displayed when a business component field specifies a Pre Default Value with a timestamp that is not encapsulated in double quotes.
3) When querying on date fields in the Siebel UI using the same date format specified by the application locale, but the date separator is incorrect, then this causes an error. For more information on the Date Separator, please refer to Siebel Bookshelf version 7.7 > Applications Administration Guide > Initial Setup > Setting Up Locales.
4) When using the Find drop-down list in pick applets, where a field is selected based on date and time format, and then an error is displayed. For example, Account Entry Applet - Price List pick field - and then searching on Start Date. Sometimes error SBL-DAT-00403 is displayed advising the user to encapsulate the search criteria in quotations; however the above error message still appears.
5) Querying on Find fields in the Siebel Search Center that are based on dates can cause errors if the query string does not match the application default date format.
6) An error might be generated when importing an XML formatted message into the Siebel application via Integration Objects, especially when the IO Field is set to DTYPE_TEXT and the value in the XML message is encapsulated in double quotes.
7) The EAI Siebel Adapter does not perform date or time validation rather this is done at the user interface layer and therefore if the format is incorrect or contains invalid characters no error appears. In some cases, for example where the year is specified as 2 digits as opposed to 4 digits, then this type of validation is handled by the Siebel object manager as described in Siebel Bookshelf version 7.7 > Siebel eScript Language Reference > Siebel eScript Language Overview > Siebel eScript Programming Guidelines (Use four-digit years in dates).
8) A workflow process might throw an error if it specifies the Match Date property on Update operations, for example,
Field Name: Suspended Date
Type: Expression
Value: [&Match Date] + 30
9) An error might occur when creating a Workflow Policy Condition that involves a comparison between two workflow policy columns based on a date data type.
10) A campaign load might fail if the format of date fields is incorrect.
Corrective Action
Below are the corrective actions to try for the reported causes:1) It is recommended to convert the date into the respective format specified by the regional settings, for example "dd.mm.yyyy", and then call the SetFieldValue with the converted value as described in Technical Note 230. For more information on the script syntax, please refer to Siebel Bookshelf version 7.7 > Siebel Object Interfaces Reference > Interfaces Reference > Business Component Methods > SetFormattedFieldValue Method.
Change Request 12-I54UKV was logged to address this product defect, which has been fixed in Siebel 7.7.
2) The Pre Default Value property should be specified using the format "hh:mm:ss" and encapsulated in double quotes. The field itself should be based on the DTYPE_TIME Date Type. Please refer to Technical Note 539 for more information on this matter.
3) Ensure that the Date Separator specified under Application Administration > Locale - reflects the same separator specified in the Short Date Format.
4) As a workaround when performing a query in a pick applet on a date field, use the Query button as opposed to using the Find drop-down list. Change Request 12-PDZ7T2 was logged to address this product defect.
5) Scripting could be used as an alternative in order to validate the search strings entered in the Find fields. Change Request 12-L5URHJ was logged to address this product defect.
6) Either, a) specify the IO Field as DTYPE_DATETIME (no double quotes needed in the XML) using format “YYYY/MM/DD HH:MM:SS” or specify “HH:MM:SS” (without quotes) as the XML element value. In addition, the Length property of the integration component field should be removed, because when an integration object and integration component is generated, the Length property of the integration component field with DTYPE_DATETIME as Type is set to null by default or b) change the Data Type of the integration component field to DTYPE_TEXT and specify the value without quotes. Ensure that the Length property is set correctly, for example from 7 to 8 on integration component field and the BC field.
7) Ensure that date values are passed using the correct format to the EAI Siebel Adaptor. Change Request 12-MDI6LC has been logged to address a product defect related to how the same data validation should be present in the EAI Siebel Adaptor as in the Siebel UI.
8) Ensure that the process property called Match Date has the Data Type set to Date as opposed to String. For more information, please refer to Siebel Bookshelf version 7.7 > Siebel Business Process Designer Administration Guide > For Developers: Workflow Process Steps > About Process Properties > Defining Process Properties.
9) Please refer to FAQ 1335 where it states that the comparison of two columns in a workflow policy condition is currently not possible in Siebel 7. Change Request 12-K9BP8N was logged to address this product enhancement request. Instead use a workflow process to do this comparison.
10) Under Marketing Administration> External Data Mapping > Tables - the field expression should be amended to return a string using the format "mm/dd/yyyy hh:mm:ss".
No comments:
Post a Comment