Yep! Imagine that also... I guess it could be described as a primitive and rustic way of doing what is done with JavaScript/TypeScript on MVVC model.
Actually, I don't assume Winbox has the full knowledge of whats is being done in RouterOS.
I tried to be careful to use verbs and constraints that made it clear that the result is not assertive, but rather rough and estimated. But my English isn't good enough(yet) to allow me to think everything in English. So I used a translator, and it may be that my intention to make "rough and estimated" explicit was lost in translation.
I believe the "Possible references" case is the most explicit of all in this regard.
In my opinion, the "correct" way to perform this search I suggested is the way Cisco Call Manager does it in its "Dependency Records" feature. Everything is in a relational database, and the system relies solely on the database's referential integrity and queries it using PKs and FKs in the database.
Below are images of Cisco Call Manager and the dependency records function.
But in RouterOS, this type of strict implementation based on entity relationships is impossible.
The network configuration scenario itself requires that relationships between objects have weak referential integrity. An example of this is the YANG model.
So, the only alternative is to perform an approximate, rough search.
A "pipe-grep" in the configuration file, searching for the string.
Is the result perfect? No! But it's better than nothing.
Network engineers, network operators, old-school programmers, and all the animals of that species we belong to tend to only accept unequivocal associations. And in the real world, that's intangible.
For me, accepting that hurts!
But we can achieve decent results with good inferences and approximate estimates. The prerequisite for this is the use of good methodologies in the process.