If I were doing it via ARS I would run an escalation, NOT a filter, on the SHR:People form (or whatever other equivalent form you are using to maintain your user database if its a home grown application). And a similar filter on the User form to change the login field to loser case..
A Filter running would be triggered only on a server event on that record, such as a submit, Modify, Delete etc... which is why you are not seeing your filter firing...
Cheers
Joe D'Souza
Remedy Developer / Consultant,
BearingPoint,
Virginia.
----- Original Message ----
From: Kathy Morris <[EMAIL PROTECTED]>
To: [email protected]
Sent: Friday, August 18, 2006 4:06:56 PM
Subject: Lowercase Login field
**
__20060125_______________________This posting was submitted with HTML in it___
From: Kathy Morris <[EMAIL PROTECTED]>
To: [email protected]
Sent: Friday, August 18, 2006 4:06:56 PM
Subject: Lowercase Login field
**
Hi,
Last night I spent a significant amount of time reading archived messages on this subject, the ARS guide, etc.... and my workflow is still not working.
We have several users with inconsistent formats - bsmith, TJackson, rVince, and our requirement is for a consistent lower case format.
I created a filter which called the function LOWER ($Login Name$) passing the value LOWER($Login Name$) into the field $Login Name$. Not working. A thread had mentioned a direct SQL statement, which I did not have the syntax for. Also there was mention of _javascript_ thru midtier. I am trying to get this to work on the client via the user tool.
Is there a way to modify previous user login ids to lower case.
I know I can set a pattern of $LOWER$ on the field for future created login ids.
Is there a way so that when searching on fields, the case does not matter? I think someone said "no, and live with it." Just need to confirm.
