You need to sign in to do that
Don't have an account?
Russel Mendoza
Flow question. Don't accept spaces on inputs.
Hi Team,
I have a simple question with regards on how not to accept spaces on fields. Basically I created this field in flow(PFP) that accepts only 10 - 15 alphanumeric characters which works fine. Now I''m trying to add another validation that checks if the input has a spaces between them but unfortunatly the "contains" syntax is not working for me or am I doing something wrong in here? When I added this syntax it ruins the whole validation rule and it doesn't accept any thing.
Validation: AND(LEN({!PFP}) >= 10 && LEN({!PFP}) <=15, REGEX({!PFP},"[\\p{L}\\s\\d]*$"), CONTAINS({!PFP},"[\\s]"))
Any help will be greatly appreciated. Thanks in advance.
I have a simple question with regards on how not to accept spaces on fields. Basically I created this field in flow(PFP) that accepts only 10 - 15 alphanumeric characters which works fine. Now I''m trying to add another validation that checks if the input has a spaces between them but unfortunatly the "contains" syntax is not working for me or am I doing something wrong in here? When I added this syntax it ruins the whole validation rule and it doesn't accept any thing.
Validation: AND(LEN({!PFP}) >= 10 && LEN({!PFP}) <=15, REGEX({!PFP},"[\\p{L}\\s\\d]*$"), CONTAINS({!PFP},"[\\s]"))
Any help will be greatly appreciated. Thanks in advance.
So your formula will be exactly this. This REGEX will only allow alphanumeric characters and not allow any spaces.
All Answers
Your validation formula should be simply this.
Kindly mark as an asnwer if that works !
This code basically works for me> AND(LEN({!PFP}) >= 10 && LEN({!PFP}) <=15, REGEX({!PFP},"[\\p{L}\\s\\d]*$"))
The code above works it's just that I'm having problem on inserting this new syntax for not to accept blank spaces.
So your formula will be exactly this. This REGEX will only allow alphanumeric characters and not allow any spaces.
What's the error that you are getting ?
I have used it in a flow and it works perfectly fine for me when I test it out.
In my case, the name of my field is "PFP" and I have used it as it is without any curly braces.