|
|
| Reporter | BCP Software | Assigned To | BCP Software | |
|---|
| Priority | normal | Severity | major | Reproducibility | have not tried |
|---|
| Status | resolved | Resolution | fixed | |
|---|
| Target Version | 12.4.2 | Fixed in Version | 12.4.2 | |
|---|
|
|
| Summary | 0003484: Merging legacy expressions fail |
|---|
| Description | When two models contain an expression with the same expression code as if they are both created in their own model, the merging into a third leads to confusing results. |
|---|
| Steps To Reproduce | IG1 (# 400): [OTFT1] O123
IG2 (# 987): [OTFT1] O123
After merging IG2 into IG3 the rsult is:
IG3: [OTFT1] O123 (Namespace IG2#987)
After merging IG1 into IG3 the rsult is:
IG3: [OTFT1] O123 (Namespace IG1#987)
Workaround:
Replace O123 in either IG1 or IG2 with the correctly owned OTE.
Then merge into IG3.
|
|---|
| Additional Information | Legacy code used to merge on ExpressionCode and OTFT. This is replaced by merging on SyncLinks to make sure all expressions are unique where they are created. The merge however needs to take into account old versions and newer versions of models, and therefor: if it couldn't find a matching synclink, it would fallback to matching on expressioncode and otft. This can no longer be maintained. |
|---|
| Tags | No tags attached. |
|---|
|
|
| CaseTalk Edition | unknown |
|---|
|
|
