Creating a field with the same name on the same parent/child hierarchy (i.e., task,incident) is incorrectly allowed. This results in the following issues:
- Using such a field with two (or more) Dictionary records on the same parent/child hierarchy will behave erratically.
- Each Dictionary definition will be mapped to a database field via separate Storage Aliases, but the platform will see them as a single field, meaning that updates to records using these fields will sometimes be written in one database field and sometimes in the other. From the end user perspective, their updates will appear to be lost because after submitting a value, the field is loaded as empty, or the field cannot be updated because it loads with the old value after an update is made.
Steps to Reproduce
Access two base system instances.
On instance A, capture the creation of field incident.u_test in an update set.
For more information, see the product documentation topic " target="_blank" rel="nofollow">System update sets.
Try to create field task.u_test and notice the error message.
On instance B capture the creation of field task.u_test in an update set.
Try to create field incident.u_task and notice the error message.
Close complete both update sets on Instance A and B, and export to XML.
Import the update set from instance B to instance A and commit it.
Note that you have both incident.u_test and task.u_test fields.
Import the update set from instance A to instance B and commit it
Note that you have both task.u_test and incident.u_test.
Try storing values into these fields and observe the inconsistent updates.
Expected results: OOB Business Rule 'Validate Table name and Element name' should prevent this with a message 'Column ... already exists in this table or a table extended from it'
Actual results: When an update set is committed, this check is not done, and the field with the same name on the same parent/child hierarchy can be created.
If you are able to upgrade, review the Fixed In field to determine the versions that have a permanent fix. Otherwise, contact Customer Support for remediation assistance.
Related Problem: PRB733389