nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Validation reg ex for Texarea is failing

Spencerspins

Sorry for the double post that other thread just not allowing me to edit it. Can a moderator please remove it?

I have the following regex for a textarea o limit characters to 100 max, but its failing with this meaasge

Root cause:
SAX Parse:The value of attribute "validation-regex" associated with an element type "textarea" must not contain the '<' character.

regex
validation-regex="^[\s\S]{1,1000}$"

if I remove the $ error goes away but regex will not work to limit the characters to 100. Could be because we are using ipl file to write out DCT. Is there any alternative to this other than FormAPI character count?

Find more posts tagged with

Comments

nipper

This code will work directly in a DCT, but it will not work if you use an inline (Perl) because $ is a Perl special character. If the latter, you can escape it \$.

Spencerspins

Thnaks nipper \$ will allow me to edit DCR without errors but regex will not work to limit the characater count to 100

nipper

Is this a Perl inline ?

nipper

Thnaks nipper \$ will allow me to edit DCR without errors but regex will not work to limit the characater count to 100

And I assume you mean 1000 characters because that is what your regex limits

ISCBorisB

Thnaks nipper \$ will allow me to edit DCR without errors but regex will not work to limit the characater count to 100

No, {1,1000} clause will not allow you to limit your count to 100. It will dutifully limit it to 1000 though.

Nipper is undoubtedly correct. $" is (one of the) special Perl variables, Array to String conversion separator. If it is unescaped, Perl
evaluates this portion of your regex to a space ( $" default). The end result is something like < ...validation-regex="^[\s\S]{1,1000} />,
note disappeared $ sign and closing quote! Thus your Parser error follows and so on.

Long story short, escape "$" sign (or use non-evaluating quoting) and continue to debug...

Spencerspins

Sorry guys it is in fact 100, I pasted wrong regex
validation-regex="^[\s\S]{1,100}$">

and it is in-line perl, escaping $ allows to edit the DCR but regex fails. Thanks for all the replies

ISCBorisB

it is in-line perl, escaping $ allows to edit the DCR but regex fails

Execute your inline from CLT and analyze the output. See if the regex comes out as you expect.

Judging by your posts, I can practically guarantee that you will find other problems as well. For example,
if you do not escape reverse slash itself, "[\s\S]" evaluates to "[sS]" ( Escape S evaluates to just S !) and so on.

Point is, you only think that you get "^[\s\S]{1,100}$" from your inline Perl. Very good chances are that you don't.

Adam Stoller

You may need to double-escape the $ - i.e.:

\\\$

If the code goes through more than one pass of evaluation it is possible that the first escape gets through the first pass but gets mis-interpreted in a second pass.

Just a guess.

The better alternative would be to use FormAPI to validate the textarea - it will let you type more than 100 characters, but it can prevent them from saving the DCR if there are more than 100 characters.

imageToMasterPageFooter.rptdesign

Spencerspins

I will try that, Thanks

Spencerspins

Execute your inline from CLT and analyze the output. See if the regex comes out as you expect.

Judging by your posts, I can practically guarantee that you will find other problems as well. For example,
if you do not escape reverse slash itself, "[\s\S]" evaluates to "[sS]" ( Escape S evaluates to just S !) and so on.

Point is, you only think that you get "^[\s\S]{1,100}$" from your inline Perl. Very good chances are that you don't.

Yea You are right. I think I should just stick to FORMAPi