Find subnetworks tool is now case sensitive

DamienPyne

We are in the process of migrating from Ent10.8.1, Pro2.7.4, UN3, to Ent 11.1, Pro3.1.5, UN6 and our testers have found this issue where the find subnetworks tool is now case sensitive.

Has anyone else found this? Is this meant to be functioning like this in Pro3.x? Obviously not an issue if the subnetwork names are all lowercase or uppercase and searching is only conducted this way. But where the user creates the name in title case this can be problematic.

RobertKrisher

The behavior of the find subnetworks pane shouldn't be changed from the behavior in 2.7.4. If you look at the SQL created by the pane (click the SQL toggle) you'll see that they both use the database command (e.g. SUBNETWORKNAME LIKE '%one%'). The like operator is case-sensitive in some database systems, if you're using one of these databases then you will need to adjust your SQL to do something like UPPER(SUBNETWORKNAME) LIKE '%ONE%'.

View solution in original post

RobertKrisher

The behavior of the find subnetworks pane shouldn't be changed from the behavior in 2.7.4. If you look at the SQL created by the pane (click the SQL toggle) you'll see that they both use the database command (e.g. SUBNETWORKNAME LIKE '%one%'). The like operator is case-sensitive in some database systems, if you're using one of these databases then you will need to adjust your SQL to do something like UPPER(SUBNETWORKNAME) LIKE '%ONE%'.

DamienPyne

Thanks @RobertKrisher I will pass this information back to the team and get back to you.