[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 704
  • Last Modified:

dissallow / ban decimal (period) character in text field in Livecycle

Hi there,

I have a text field in Livecycle and i want to disallow any alphabetical characters (i must keep it a text field).

For the validation pattern I have used the "999999999" system but decimals are still permitted.

How can i parse through the field at validation and stop decimals getting through, or stop being entered entirely?

Regards,

Darren
0
SWS001
Asked:
SWS001
  • 5
  • 4
1 Solution
 
SWS001Author Commented:
I suppose I should have said also that only numerical values are permitted.

It must remain a text field though.

Regards,

Darren
0
 
Karl Heinz KremerCommented:
Are you getting a validation error message when you tab out of the text field? Try using the same pattern for Display, validation, entry and data.
0
 
SWS001Author Commented:
eh?

I just want to be able to stop people being able to enter a decimal, as it appears even though the "999.." pattern is used to say "only numbers please" it's still counting the decimal stop as a number.

The decimal needs to be removed or not allowed.
0
The new generation of project management tools

With monday.com’s project management tool, you can see what everyone on your team is working in a single glance. Its intuitive dashboards are customizable, so you can create systems that work for you.

 
Karl Heinz KremerCommented:
Yes, I understand. And when I use the same pattern "text{9999}" for Display, Validation, Edit and Data, I get a validation error when I enter a decimal point. It only allows digits. So, to me this falls into the category of "not allowed".
0
 
SWS001Author Commented:
"text{9999}" ? I thought to only allow number it was just the characters 99999 you used.

I'll try out your method now
0
 
Karl Heinz KremerCommented:
Which version of Designer are you using? I suspect it's not the latest (8.2).
0
 
SWS001Author Commented:
version 8.0

It works but unfortunatley breaks the other field.

I'll tell you in more detail what I'm trying to do.

Basiclaly the field should only be able to receive:

12 numerical digits ie. 999999999999

or

12 with a plus before ie. "+"999999999999

or

12 with a minus before  ie. "-"999999999999

Using your method does indeed stop the decimal being used, however then i am getting errors with the + and Minus which before seemed to work fine.

I've tried:

text{999999999999} | text{'+'999999999999} | text{'-'999999999999}

and also: text{999999999999} | '+'text{999999999999} | '-'text{999999999999}

But these dont seem to work. I'm sorry but I'm new to this.

I also have some code running on the validate as well (that was put in place b one of our devs) It looks like this:

"+" && 0 <= this.rawValue && this.rawValue <=999999999999 or "-" && 0 <= this.rawValue && this.rawValue <=999999999999 or 0 <= this.rawValue && this.rawValue <=999999999999

So any ideas why it fails on the + or minus with the updates validate pattern field, but not with the old ones? It seems i can either have + and - working as validation but the user can enter "." or the other way around.
0
 
SWS001Author Commented:
any update on this?

I really need help on this matter as am a beginner in this field.

Regards,

Daz
0
 
Karl Heinz KremerCommented:
No, this goes too deep into Designer. I've only played with Designer forms, my expertise is in AcroForms.  
0

Featured Post

Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

  • 5
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now