Troubleshooting
Problem
The business key attributes of the child business objects in a party cannot be updated using the coarse-grain party-level transactions. However the same attributes of the child business objects can be updated by using the granular transactions.
Symptom
Here is a scenario that illustrates this problem:
- Add an organization with a name and address.
- Update this organization using an updateOrganization transaction. Specify updates to the name usage type and organization name, as well as to the address usage type and address line 1. This transaction fails with an error that indicates that updates to the business keys are not allowed.
- With the granular transactions updateOrganizatioName or updatePartyAddress, update the same attributes as in step 2. These transactions successfully update the records.
Cause
The default implementation for the rule 18 invalidates any supplied update to the business key attributes of the child business objects for the party. This rule is invoked using coarse grain party-level transactions such as updateParty, updatePerson, and updateOrganization transactions.
However, the same logic is not enforced for the granular transactions such as updateOrganizationName, updatePartyAddress, and so forth.
Resolving The Problem
The work around depends on the implementation decisions made with regard to updating the business keys.
- If the updates to business key attributes are desired, the default Java implementation of the rule 18 must be customized to allow such updates.
- Otherwise, new behavior extensions should be implemented for the party granular update transactions to disallow any update to the business key attributes.
Was this topic helpful?
Document Information
Modified date:
27 April 2022
UID
swg21639751