SYMPTOM:
Logical tables mappings are not correctly updated after migrating an attribute with Strategy Object Manager 9.4.1. As a result, the source tables list in the attribute editor is different in the source and target projects.
STEPS TO REPRODUCE:
These are the steps to reproduce the issue:
1. Create a logical table in the source project.
2. Create an attribute that is mapped to the logical table created in Step 1 as well as other relational tables. Update schema.
3. Create an Object Manager package that contains the attribute and all its dependencies. Set the action to "Replace" or "Force Replace".
4. Import the package into the target project. Update schema.
5. Edit the attribute in the source project, and remove the logical table from the Source Tables list. Update schema.
6. Create an Object Manager package that contains the attribute and all its dependencies. Set the action to "Replace" or "Force Replace".
7. Import the Object Manager package into the target project. Update schema: the logical table that has been unmapped in the source project still appears in the attribute source tables list of the target project.
This issue does not occur when:
- Adding a new source table (logical or not) in the source and migrating the attribute.
- Unchecking a non-logical table from the list of source tables and migrating the attribute.
CAUSE:
This is a known issue in Strategy Object Manager 9.4.1.
ACTION:
This issue has been addressed in Strategy Object Manager 9.4.1 Hotfix 3. Upgrade to that version to take advantage of this fix.
