SBL-UIF-00299

APPLIES TO:

Siebel Tools - Version 7.7.2 [18325] and later
z*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (Enterprise)
Version: 7.7.2 [18325]
Database: Microsoft SQL Server 2000 SP3
Application Server OS: Microsoft Windows 2000 Professional
Database Server OS: Microsoft Windows 2000 Professional

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

Checked for Relevance on 30-Jan-2014

SYMPTOMS

In Service Request Contact Last Name and LOB (a custom field) are required fields. We have exposed these fields on the Service Request Add Applet in the Service Request Homepage. We are facing following two problems:

1. Whenever there are two contacts with same Last Name and we try to pick one out of these in the Add Homepage Applet and click "Add & Go" without filling the other required field it gives us the following error message:

Wrong field values or value types detected in field Last Name. Please re-enter your field values. If you need additional assistance, please refer to the documentation.(SBL-UIF-00299)

However, it should give the following the error message:

'LOB' is a required field. Please enter a value for the field.(SBL-DAT-00498)

We get this error messages correctly if we pick up a contact where single contact record exists with the particular Last Name.

2. After it gives us the "Wrong field values" message, if we click on the contact last name pick applet again it just shows contacts with the last name that we picked up last time.

We have been successful in replicating this error on Vanilla Application.

CAUSE

The behavior described by the customer is reproducible using standard Siebel application version 7.7 against the sample database. Here are the steps:

1. Click the "Opportunities" screen tab to access the "Opportunities Home" page view.
2. In the "Add" applet open the "Pick Account" pick applet from the account field.
3. Select "SKF" (there is only one account with this name) and click "OK".
> This error will occur:
- - -
'Opportunity' is a required field. Please enter a value for the field.(SBL-DAT-00498)
- - -

This error is expected since this field is required at BC level.

4. Open again account pick applet and select "Harley-Davidson Inc" (there are several accounts with this name) and click "OK".
5. Select account "Harley-Davidson Inc" (there are several accounts with this name) and click "OK".
6. Click the "Add & Go" button:
> The following error occurs
- - -
Wrong field values or value types detected in field Account. Please re-enter your field values. If you need additional assistance, please refer to the documentation.(SBL-UIF-00299)
- - -

This error is not expected.

7. Open again the account pick applet:
> Only the accounts named "Harley-Davidson Inc" appear in the applet (15 records)

BUG 10493528 has been logged to address this product defect.

SOLUTION

Note that this behavior is also reproducible in the "Add" applet of the "Contacts Home" page view. However it does not occur in the "Orders Home" page view. The reason is a user property named 'Mirror Add Error Req Field'. This user property is defined in BC 'Opportunity Home Add Virtual' and 'Contact Home Add Virtual' and is set to "Write Mirror". It does not exist however in BC 'Order Entry - Orders Home Add Virtual'. When this user property is inactivated in the 2 BC mentioned above the issue does no longer occur.

Note however that inactivating the 'Mirror Add Error Req Field' user property produces another unexpected behavior addressed by BUG 10482123 and described in Note 495090.1:
- - -
In the Quick Fill template on the Activity Home Page, the customer experienced that not entering a value in a mandatory field and clicking the 'Add&Go' button caused an expected error message, however prior to invoking the error message the values entered in the other fields were not retained.
- - -

If the 'Mirror Add Error Req Field' user property is kept active then the solution to avoid the issue described above is to ensure that the required fields are filled before clicking the "Add & Go" button.

APPLIES TO:

Siebel Tools - Version 8.0 [20405] and later
z*OBSOLETE: Microsoft Windows Server 2003
Product Release: V8 (Enterprise)
Version: 8.0 [20405] FRA Retail
Database: Oracle 10.2.0.1
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-3406577713.

Checked for Relevance on 24-February-2015

SYMPTOMS

I need to access the standard field LOY Member.Contact Postal Code in read-write mode via script and/or UI. The field is displayed correctly but can't be updated. It works as if it tries to set the destination field of the first level MVLink (LOY Member/Contact) on the destination bus comp from the second level MVLink (Contact/CUT Address).

The only relevant modification to vanilla pertaining to this issue has been setting popup update only=FALSE on the LOY Member/Contact MVLink.

Is updating nth-level (n >= 2) MVFields a supported feature or is it considered bad design? I am trying to achieve this behavior for performance (one less query in one web service) / number of clicks (in the UI) reasons. Please advise.

CAUSE

Bug 10527969

The behavior described has been reproduced using standard Siebel application version 8.0 SIA against the sample database. Here are the steps:

# Using Tools:

Expose standard MVF 'Contact Postal Code' on applet 'LOY Member List Applet'

# Using Siebel Loyalty:

1. Click the "Loyalty Members" screen tab
2. Update the field "Contact Postal Code" and try saving the record
> You will get these errors:
- - -
[1] Wrong field values or value types detected in field Contact Postal Code. Please re-enter your field values. If you need additional assistance, please refer to the documentation.(SBL-UIF-00299)
[2] Field 'Personal Postal Code' does not exist in definition for business component 'CUT Address'.

Please ask your systems administrator to check your application configuration.(SBL-DAT-00398)

SOLUTION

In BC 'LOY Member' the MVF 'Contact Postal Code' is mapped to field 'Personal Postal Code' in BC 'Contact' via the MVL 'Contact'. In BC 'Contact' the field 'Personal Postal Code' is a MVF mapped to field 'Postal Code' in BC 'CUT Address' via the MVL 'Personal Address'.

> There are therefore 2 levels of MVF.

- Same behavior using other MVFs mapped to a MVF (e.g. 'Contact City' mapped to 'Personal City' mapped to 'City').

- Same behavior using other BC, e.g. 'Action' that has a similar 'Contact' MVL (test performed by adding a new MVF named 'Contact Postal Code' and mapped to field 'Personal Postal Code' and exposing it on applet 'Activity List Applet With Navigation').

- Same behavior using versions 7.8.2.6 SIA, 7.7.2.8 SIA and 7.5.3.15 SIA.

NOTE: Given the error message the following has been tested: add in BC 'CUT Address' a new field named 'Personal Postal Code' and mapped to the same column as field 'Postal Code', namely ZIPCODE.

With this configuration it is possible to update the field "Contact Postal Code" and save the record without getting any error but the change is not taken into account. In fact the field is set back to its initial value when you save the record.

Bug 10527969 /CR 12-1KEJ2FB has been logged to address the unexpected behavior observed when trying to update directly an MVF mapped to another MVF.

The suggestion is to update the MVF 'Contact Postal Code' via the 'LOY Member Contact Mvg Applet' by exposing the field 'Personal Postal Code'. This MVG applet, based on BC 'Contact', is invoked from the MVF 'Contact Last Name' in the UI.

For an update via scripting you can use the GetMVGBusComp method to get the MVG BC associated to field 'Contact Last Name', namely BC 'Contact', and query it using the appropriate methods (SetViewMode, ActivateField, ClearToQuery, SetSearchSpec, ExecuteQuery,...)

APPLIES TO:

Siebel Financial Services CRM - Version 8.1.1.11.11 [IP2013] and later
Information in this document applies to any platform.

SYMPTOMS

On : 8.1.1.11.11 [IP2013] version Open UI

On Dedicated:

Issue can be seen once you change the DateFormat in Regional Settings with Short Date: "dd/mm/yyyy"

The application will use "mm/dd/yyyy" for all the applets except Currency Popup applet which use "dd/mm/yyyy".

Therefore on Currency Popup Applet (Write Record), validation will raise the errror.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Navigate to Events Plan
2. Drill-down on child applet
3. Go to Requested Budget field
4. Fill up the Amount field;
Trying to go back on previous applet is no more possible and the error raise

ERROR
-----------------------
"[1]Wrong field values or value types detected in field XXXX. Please re-enter your field values. If you need additional assistance, please refer to the documentation.(SBL-UIF-00299)
[2]The value '11-23-2001' cannot be converted to a date time value.(SBL-DAT-00359)"

CAUSE

Code Defect logged under Bug 20569875 - SBL-UIF-00299 ERROR WHEN USING CURRENCY APPLET
 

SOLUTION

 Bug is currently under work