|
|
This is due to code which takes into account transitioning models. Transitioning to SyncLink alignment. These are not always in place on older models, and therefor should match upon expcode still. In this case the models are provided with SyncLinks, but the matching on ExpCode still activates. That should be prevented in case SyncLinks are detected in the models. |
|
|
|
A workaround may be to Replace the offending OTE with a different OTE which already pre-existed in the model. This removes the ExpCode from existence and prevents a potential match while merging on ExpCode. |
|
|
|
Legacy functions which find OTE's which only map to a different OTFT through matching ExpCode and not on SyncLink, are now handled as unmappable expressions. Therefor these cases are handled as new expressions. This leads to OTFT's partially mergeable instead of getting ignored completely. |
|
|
|
Closing automatically, stayed too long in resolved state. Feel free to re-open with additional information if you think the issue is not resolved. |
|
