Hi,
I just want to say that Mahesh suggestion is definitely the way to go.
The FLTR-Run-If (with a possible ACTL-shadow) should read:
('Field' LIKE "%[^A-Za-z0-9-_]%")
And then give you an appropriate error message.
This should work on any DB, as it has nothing to do with the database, it
is evaluated internally within the AR System.
The initial ^ is the negator (NOT) character.
This is not the same thing as (NOT 'Field' LIKE "%[A-Za-z0-9-_]%"), as
this would first find a match of the characters, and then negate it.
In the example "?A?" it would find the "A" and then negate it. In the
first suggestion above though it would find the first "?", which is a bad
character.
In other words the format [^...] is the only way to go.
The only thing I am not sure about is the dash-character (-), as it
specifies a range... You could try "%-_A-Za-z0-9]%" instead. Others have
suggested a backslash, but I do not think that will work here... Try
removing the dash altogether to see if you can get the rest to work at
least.
Best Regards - Misi, RRR AB, http://www.rrr.se
Products from RRR Scandinavia (Best R.O.I. Award at WWRUG10):
* RRR|License - Not enough Remedy licenses? Save money by optimizing.
* RRR|Log - Performance issues or elusive bugs? Analyze your Remedy logs.
Find these products, and many free tools and utilities, at http://rrr.se.
> 'Field' LIKE "%[^A-Za-z0-9-_]%"
>
> Thanks
> Mahesh
>
>
> On Tue, Jun 14, 2011 at 1:30 PM, Kemes, Lisa <lisa.ke...@te.com> wrote:
>
>> **
>>
>> I need to check a character field to make sure that the string in the
>> field
>> is alphanumeric and the only special characters that are allowed are a
>> hyphen “-“ or an underscore. No spaces allowed either.
>>
>>
>>
>> I’ve tried a bunch of workflow and it’s just not working for me.
>>
>>
>>
>>
>>
>> *Lisa Kemes*
>> AR System Developer
>> TE Information Systems
>>
>> Global Infrastructure and Ops
>> +01 717 810 2408 tel
>> +01 717 602 9460 mobile
>> *lisa.ke...@te.com*
>> MS 161-43
>>
>> P.O. Box 3608
>>
>> Harrisburg, PA 17105-3608
>>
>> [image: Description:
>> http://www.tycoelectronics.com/images/socialmedia/smallTElogo.gif]<http://www.te.com/>
>> www.te.com
>>
>>
>> [image: Description:
>> http://www.tycoelectronics.com/images/socialmedia/twitter.png]<http://twitter.com/teconnectivity>[image:
>> Description:
>> http://www.tycoelectronics.com/images/socialmedia/facebook.png]<http://www.facebook.com/teconnectivity>[image:
>> Description:
>> http://www.tycoelectronics.com/images/socialmedia/flickr.png]<http://www.flickr.com/photos/teconnectivity/>[image:
>> Description:
>> http://www.tycoelectronics.com/images/socialmedia/linkedin.png]<http://www.linkedin.com/groups?gid=1591657>[image:
>> Description:
>> http://www.tycoelectronics.com/images/socialmedia/youtube.png]<http://www.youtube.com/teconnectivity>
>>
>>
>> _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_
>
> _______________________________________________________________________________
> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
> attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
>
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
