idea Add RegEx support to Arcade in ArcGIS Pro Ideas

Add RegEx support to Arcade

AJR — Wed, 02 Mar 2022 16:22:47 GMT

Please add regex support within arcade expressions. This would be really useful for defining attribute constraints. As an example, I can use the function below in Python to check to see if a string is a guid, it would be nice to be able to use a regex within an arcade attribute constraint to accomplish a similar task.

Re: Add RegEx support to Arcade

JoshuaBixby — Fri, 19 Nov 2021 16:37:15 GMT

@AJR, you make good music and do GIS too, impressive. 🙂

Adding regex support to Arcade is a great idea, definitely worth a vote, but it will be quite a lift for Esri to do it. I will cross my fingers, just not hold my breath.

Re: Add RegEx support to Arcade

OlabanjiAladejana — Fri, 18 Mar 2022 07:54:35 GMT

Yes. This will definitely be nice to have.

Re: Add RegEx support to Arcade

feralcatcolonist_old — Mon, 09 May 2022 18:32:37 GMT

A Google search for something I was sure already existed led me here. So let's make it happen!

Esri, if you're wondering about the use case...

I'm making an attribute rule to concatenate NENA Address components to make a full address. Apparently, an address suffix that is an alpha ("A", "B", "C") needs to be concatenated to the address number without a space; whereas, a numeric ("1/2", "3/4") needs a space

https://gis.ny.gov/streets/documents/MoreStreetAddressParsing-2014.pdf

Re: Add RegEx support to Arcade

Kara_Shindle — Tue, 19 Jul 2022 18:07:25 GMT

Was just looking to add my first attribute rule and find that it only supports Arcade, not Python! I had wanted to use some regular expressions for formatting my phone numbers and email fields - something I can do on Survey123.

Re: Add RegEx support to Arcade

DavidSolari — Fri, 09 Jan 2026 16:30:09 GMT

Shocked this hasn't been at least considered, from what I know of how Arcade is implemented this is trivial due to language-level support in JavaScript. If ESRI is concerned with sloppy expressions causing load issues in ArcGIS Online (very difficult as regex is supposed to evaluate client-side, but I'm sure there's a way to cause mayhem somehow) then limiting their Profile set as a trial would be a good start.