Applies to:
Siebel Tools - Version: 7.5.2.216 [16084] - Release: V7z*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (Enterprise)
Version: 7.5.2.216 [16084]
Database: Oracle 8.1.7.4
Application Server OS: Microsoft Windows 2000 Server SP 3
Database Server OS: HP-UX 11i
This document was previously published as Siebel SR 38-2777050151.
Symptoms
SBL-DAT-00294Hi,
As per Doc ID 509391.1, we weren't able to reproduce the behavior as mentioned in
the
document. We have applied 7.5.3.13 and did the same kind of configuration as explained in
above document. Here, I tried to use Business Address as Mvg BusComp and
Account as parent BusComp. Basically trying to implement hierarchial logic between Province and
State fields at the Business Address BusComp level and did the same thing for the respective MVFs
at the Account BusComp level. We were able to create a new record and save it without any error.
We couldn't create the error mentioned in the 509391.1.
So can you please let us know if it is
solved in patch 13 over pack 7.5.3 or its a prevailing issue which requires a quickfix or
something to resolve the above issue mentioned even though we were not able to reproduce. This is
just to confirm so that we don't face any issue after the upgrade from 7.5.2.216.
Please
note that our IE version is 6.0.2900.2180.xpsp_sp2_gdr.050301-1519, Update: SP2.
Cause
Popup Update Only property in Business Address MVL of Account BC is set to TRUESolution
Message 1
For the benefit of Other Readers:Requirement:
Hierarchical Pick list is defined between Country and Province in the Address Business Component. Requirement is to implement the same hierarchical logic in the Address MVF of Account BC. Hence we have defined the same pick map definitions for the Country and Province MVF in Account BC.
Resolution:
In case of the Doc ID 509391.1, the field name (HPQ Region) used in the Parent BC is different from that of the field name (Province) in Child BC (Address BC) and hence the error message. Workaround suggested is to create a calculated field with the same name (HPQ Region) in Address BC.
In this case, though the field name (Province) referred in the Parent and Child BC are same, the below 2 error message were displayed:
[1] Wrong field values or value types detected in field Country. Please re-enter your field values. If you need additional assistance, please refer to the documentation. (SBL-UIF-00299)
[2] You have tried to modify a group of fields that may have more than one value.
To edit or add field values in this group, please open the first field in the group by clicking on the multivalue field control. (SBL-DAT-00294)
Upon further research, found that this error message (SBL-DAT-00294) will be thrown when the Popup Update Only property of the MVL is set to TRUE and if someone tries to modify it.
Hence the issue was resolved by setting the “Popup Update Only” property to FALSE in Business Address MVL of Account BC and compiling changes. If the field name (Province) is same in both the Parent and Child BC, no need to create a Calculated field in the Child Bus Component.
Thanks
Siebel Technical Support
Applies to:
Siebel Tools - Version: 7.5.2.216 [16084] - Release: V7z*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (Enterprise)
Version: 7.5.2.216 [16084]
Database: Oracle 8.1.7.4
Application Server OS: Microsoft Windows 2000 Server SP 3
Database Server OS: HP-UX 11i
This document was previously published as Siebel SR 38-2777050151.
Symptoms
SBL-DAT-00294Hi,
As per Doc ID 509391.1, we weren't able to reproduce the behavior as mentioned in
the
document. We have applied 7.5.3.13 and did the same kind of configuration as explained in
above document. Here, I tried to use Business Address as Mvg BusComp and
Account as parent BusComp. Basically trying to implement hierarchial logic between Province and
State fields at the Business Address BusComp level and did the same thing for the respective MVFs
at the Account BusComp level. We were able to create a new record and save it without any error.
We couldn't create the error mentioned in the 509391.1.
So can you please let us know if it is
solved in patch 13 over pack 7.5.3 or its a prevailing issue which requires a quickfix or
something to resolve the above issue mentioned even though we were not able to reproduce. This is
just to confirm so that we don't face any issue after the upgrade from 7.5.2.216.
Please
note that our IE version is 6.0.2900.2180.xpsp_sp2_gdr.050301-1519, Update: SP2.
Cause
Popup Update Only property in Business Address MVL of Account BC is set to TRUESolution
Message 1
For the benefit of Other Readers:Requirement:
Hierarchical Pick list is defined between Country and Province in the Address Business Component. Requirement is to implement the same hierarchical logic in the Address MVF of Account BC. Hence we have defined the same pick map definitions for the Country and Province MVF in Account BC.
Resolution:
In case of the Doc ID 509391.1, the field name (HPQ Region) used in the Parent BC is different from that of the field name (Province) in Child BC (Address BC) and hence the error message. Workaround suggested is to create a calculated field with the same name (HPQ Region) in Address BC.
In this case, though the field name (Province) referred in the Parent and Child BC are same, the below 2 error message were displayed:
[1] Wrong field values or value types detected in field Country. Please re-enter your field values. If you need additional assistance, please refer to the documentation. (SBL-UIF-00299)
[2] You have tried to modify a group of fields that may have more than one value.
To edit or add field values in this group, please open the first field in the group by clicking on the multivalue field control. (SBL-DAT-00294)
Upon further research, found that this error message (SBL-DAT-00294) will be thrown when the Popup Update Only property of the MVL is set to TRUE and if someone tries to modify it.
Hence the issue was resolved by setting the “Popup Update Only” property to FALSE in Business Address MVL of Account BC and compiling changes. If the field name (Province) is same in both the Parent and Child BC, no need to create a Calculated field in the Child Bus Component.
Thanks
Siebel Technical Support
Applies to:
Product Release: V7 (Enterprise)Version: 7.5.2.211 [16061]
Database: Oracle 9.2.0.2
Application Server OS: Microsoft Windows 2000 Server SP 2
Database Server OS: HP-UX 11.0
This document was previously published as Siebel SR 38-1176374861.
Symptoms
SBL-DAT-00294Hello
We have a strange error in our production environment.
We are using the views
"Service Request - Helpdesk"
When we create a new SR, we add the requestor in the fileds
Requestor Last Name. It works fine but sometime for some employees, we have the following error
:
"You have tried to modify a gorup of fields that may have more than one value. To edit or
add field values in this group, please open the first field in the group by clicking on the
multivalue field control".
To select the employee, we are using the pick applet "Pick
Requestor" ("SR Employee Pick Applet").
These employees seem normal. I do not understand
why there is this error.
The only common point is that they have several positions.
But for
some users with several positions, it works.
Do you have an idea ?
Regards
Solution
Message 1
For the benefits of the other readers:Intermittenly, when picking certain employee to the Requestor Last Name control in Service Request > My Service Requests - Helpdesk view, the below error message will be encountered:
"You have tried to modify a group of fields that may have more than one value. To edit or add field values in this group, please open the first field in the group by clicking on the multivalue field control."
According to research, the behavior was found to be specific to picking employees who are associated with multiple positions and multiple addresses. When attempting to pick an employee who has multiple positions assoicated to it and where each position has multiple addresses associated with it, the above error message will be generated when the employee is picked as the requestor for the service request.
Change Request 12-JH21U4 has been logged to report on the above behavior.
[1/3] To be continued ->
Message 2
[2/3] <- Continue ->According to testings, the error message will be eliminated when the below pick maps are deactivated from the Requestor Last Name field in Service Request business component:
- Requestor City
- Requestor Country
- Requestor Postal Code
- Requestor State
- Requestor Street Address
According to research, the above pick maps have been configured under the Requestor Last Name field to bring over the address related data of the requestor to the service request record. When they are deactivated, the address related data of the requestor will not be brought over to the service request record.
If it is not necessary to show the address related data of the requestor in the service request record, the above pick maps may be deactivated to overcome the reported behavior.
[2/3] To be continued ->
Message 3
[3/3] <- Continue ->Otherwise, if it is necessary to show the address related data of the requestor in the service request record, according to testing, the reported behavior seems to be caused by the fields referenced in the above pick maps being multi-value fields.
In view of this, another possible way to workaround the reported behavior would be to configure new single value fields under the Service Request business component and modify the pick maps to pick into the new single value fields instead. To configure the new single value fields, you may consider using any unused standard extension columns from the S_SRV_REQ_X table or adding new extension columns to the S_SRV_REQ table.
Thank you.
Best Regards,
Puay Kim, Goh
Siebel Technical Support
v
No comments:
Post a Comment