Problem

When switching between sibling terms within a same termEntry, the crossReference-attributes (if any) on termEntry-level sometimes shows 'Not a valid TBX ID' , despite it's surely valid. This happens when another crossReference-attribute exists on term-level for some of these sibling terms

Solution

Validity detection logic should be amended to evaluate validity via separate SQL queries because the unified SQL query which is in use currently - is not able to hanlde this specific scenario