We are having an issue with a specific API lookup requiring exact match on case sensitivity.
Namely
/v1/record/filter/app/
We have a ProcFu portal set up and we are required to use a calculated field for the Username authentication field.
This field is requiring exact case matching on the Tape end.
Thus a user could type example@tapeapp.com with the correct PW and get access to the ProcFu app. But if they were to type Example@tapeapp.com with the same correct PW, it says they have incorrect credentials.
Can this API value be changed to not be case sensitive? Or is there a reason it has to be case sensitive for exact matching in other use cases?
