IsMatch function with pattern (Optional Comma & Space)

(0) Share

Report

Posted on by Franklin_vaz

Hi Experts,

I would like to seek your assistance on the validation syntax for an "IsMatch" function.

This is a text input field.
The user should be able to input a minimum of one 7-digit number (or) multiple 7-digit numbers [separated by a comma & a space]
Scenario1: one 7-digit number [8000000]
Scenario2: multiple 7-digit numbers [8000000, 8000001, 8000002, 8000003, 8000004]

Here is my formula,

IsMatch(
 TextInput2.Text,
 "\d{7}\,*\s*",
 MatchOptions.BeginsWith
)

This does not seem to be working, please assist. Thank you.

Categories:

Building Power Apps

I have the same question (0)

All responses (3)

Answers (1)

Verified answer

WarrenBelz 154,795 Most Valuable Professional on at

Like (2)

Report
Copy link

Link copied!
Hi @Franklin_vaz ,

Best effort below (did my head in a bit, but seems to work on test model)

With( { wText: Substitute( TextInput2.Text, " ", "" ) }, If( Find( ",", wText ) = 0, IsMatch( wText, Digit & Digit & Digit & Digit & Digit & Digit & Digit ), With( { wStrings: Split( wText, "," ) }, CountRows( Filter( wStrings, IsMatch( Result, Digit & Digit & Digit & Digit & Digit & Digit & Digit ) ) ) = CountRows(wStrings) ) ) )

Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.

Visit my blog Practical Power Apps

Was this reply helpful? Yes No
Franklin_vaz 47 on at

Like (0)

Report
Copy link

Link copied!
Many thanks, @WarrenBelz for your quick response.

Validation works, and I can understand your logic.
Here is some feedback,
The validation returns "true" even if there is no space
But it ensures each number is 7 digits and is separated by a comma at least
ignoring if a space is given or not.
Curious to ask; the test you did, was it the same case?

Was this reply helpful? Yes No
WarrenBelz 154,795 Most Valuable Professional on at

Like (1)

Report
Copy link

Link copied!

Hi @Franklin_vaz ,

The replacement of the space was "in case" one was put in as if I did not clean it up, the Split() parts could contain a space and therefore not pass validation, so yes, the results of your three points were intentional.

Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.

Visit my blog Practical Power Apps

Was this reply helpful? Yes No