Applies to:
Product Release: V7 (Enterprise)Version: 7.8.2.3 [19221]
Database: Oracle 10.2.0.2
Application Server OS: Microsoft Windows 2003 Server
Database Server OS: HP-UX 11i
This document was previously published as Siebel SR 38-3288972873.
Symptoms
SBL-DAT-00504In Search Center for the Contact BC while sorting on MVF (Account Synonym) we are getting error
"Sorting on multi valued field 'Account Synonym' is not allowed"
The Error Screen Shot is
attached (Error Number - SBL-DAT 00504).
However in Search Center for the Account BC while
sorting on MVF (Synonym) we are not getting any Error. It means we are able sort on MVF on
Account in Search Center.
Solution
Message 1
For the benefit of other readers:# Issue:
In Search Center for the Contact BC while sorting on MVF (Account Synonym) we are getting error "Sorting on multi valued field 'Account Synonym' is not allowed"
The Error Screen Shot is attached (Error Number - SBL-DAT 00504).
However in Search Center for the Account BC while sorting on MVF (Synonym) we are not getting any Error. It means we are able sort on MVF on Account in Search Center.
# Solution:
In a standard Siebel repository version 7.8 SIA the BC 'Account' has a MVF named 'Synonym' mapped to the SVF 'Name' in BC 'Account Synonym'. The MVL involved is 'Account Synonym' that is based on the 1:M link 'Account/Account Synonym'.
This MVL has 'Primary Synonym Id' as primary ID field and that is the reason why it is possible to sort on MVF 'Synonym' (no secondary query is needed to populate the MVF). This matter is discussed in the following posting on SupportWeb:
FAQ 1862: Why Do all List Applet Columns not have Sort Icons?
and also in the Bookshelf:
Configuring Siebel eBusiness Applications
Configuring Business Components
Defining Sort Specifications
In standard BC 'Contact' there is no MVF named 'Account Synonym'. This field was a custom MVF configured as follows:
Name: Account Synonym
Multivalue Link: Account
Field: Synonym
[...]
Message 2
[...]The MVL involved has 'Account Id' had primary ID field but this one cannot be used for sorting on the above MVF. The reason is the fact that this MVF is not mapped to a SVF in BC 'Account' but to a MVF mapped to a SVF in 'Account Synonym'. That means that there is another MVL involved and a secondary query is therefore needed to populate the MVF.
Note that if you expose the MVF 'Account Synonym' on a contact applet like for example 'Contact List Applet' you should see that the list column has no sort icons.
However if this not sortable field is used as Find Field and displayed on the Find Results List Applet in the Search Center the behavior is different: the sort icons are displayed at the top of the list column and if you try to sort you will get the following error:
- - -
Sorting on multi valued field 'Account Synonym' is not allowed.
Please continue or ask your systems administrator to check your application configuration if the problem persists.(SBL-DAT-00504)
- - -
Even if this error is expected it would be better to have the same behavior as in standard list applets, namely have the sort icons disabled for not sortable fields
Change Request 12-1IO2YV3 has been logged requesting this enhancement.
To allow sorting on the account synonym in the Find Results List Applet it was suggested the following:
(A) Configure the following in BC 'Contact':
- A first joined field:
[...]
Message 3
[...]Name: Account Primary Synonym Id
Join: Account
Column: PR_SYN_ID
- A join like the following:
Table: S_ORG_SYN
Alias: Account Synonym
Outer Join Flag: TRUE
with the following join specification:
Name: Account Primary Synonym Id
Destination Column: ROW_ID
Source Field: Account Primary Synonym Id
- A second joined field:
Name: Account Primary Synonym
Join: Account Synonym
Column: NAME
(B) Use the new field 'Account Primary Synonym' as Find Field for the contact Find object involved instead of the MVF 'Account Synonym'.
The customer's requirement was achieved using this suggestion.
No comments:
Post a Comment