How to deal with case sensitivity in Dataverse tables without using lower function in queries

Hello antoec 

In Dataverse, the collation settings—including whether the data comparisons are case-sensitive or case-insensitive—are defined when the environment is created and cannot be changed afterward. This means that if your environment was configured with a case-sensitive collation, you cannot later switch it to be case-insensitive through a configuration change. Therefore, to resolve issues where related fields have mismatched cases, the only practical solutions are to normalize the data—for example, by ensuring that all key values are stored in the same case—or to use computed columns that store a pre-normalized version of the data. This approach typically avoids the performance overhead of using functions like Lower() or Upper() in every query.

there isn’t a built‐in configuration setting in Dataverse to globally disable case sensitivity for text comparisons. Instead, you must ensure that the data used for linking tables is normalized so that both sides of the join use the same case.

If this is helpful please accept the answer