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; } } }

Arcade: create an array of field values

JoeBorgione

As the subject line suggests, I would like to create an array of all the values of a given field in a table. The end goal is to create an attribute rule that can check a string against the array and make sure the string is in fact part of the array.

In arcpy, I would use the da.SearchCursor and append the values of the field to a list. How does one accomplish the same basic operation in Arcade?

I never know what Geonet space to post Arcade questions to, so I'm tossing this into the ArcGIS Pro space...

Find more posts tagged with

Accepted answers

All comments

JoeBorgione

Xander Bakker‌; yes, I would/could be able to subdivide the street names by our townwhips. I'll take a look at contingent values as suggested. Updating domains in the egdb are still an issue, but I haven't yet decided how I'm going to implement the solution. I could edit a check out replica in a file geodatabase which could then use the domain there, and not worry about a domain in the egdb...

XanderBakker

Hi jborgion ,

He is using the same approach as I mentioned at the end of my initial answer (check for the count after using a filter), although his rule is properly formatted as a validation rule.

XanderBakker

Hi Joe Borgione ,

Thanks for the additional explanation on your use case. You are right, scrolling through a long list of street names is not very user-friendly. If you would have the area subdivided in areas, you could use contingent values to reduce the list of streets based on the area selected by the user.

JoeBorgione

Here is another solution provided by Chris Fox‌ that he specifically prototyped for the Address Data Management Solution as a constraint type attribute rule. I find this approach very interesting; there is a contrast in what I follow as the 'traditional' python mindset and what Chris offers here in Arcade.

// This constraint rule will ensure the full name exist in the master road name table

// Get the full name of the road. If it is null return the fullname

var fullname = $feature.fullname;
if (IsEmpty(fullname)) return fullname;

// Search the master road name table for a row matching the fullname.
// If there is no matching record raise an error preventing the edit

var masterStreetNames = Filter(FeatureSetByName($datastore, "MasterRoadName"), "fullname = '" + fullname + "'");
if (Count(masterStreetNames) == 0) {
                return {
                        "errorMessage": "Full Road Name is invalid, must be defined in the Master Road Name table."
                }
}
return true;
‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍<SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN>

JoeBorgione

Thank you for your detailed response Xander Bakker‌. With respect to your question regarding domains, they have a significant limitation in an enterprise geodatabase environment. Only the domain owner can update them. I am currently working on an implemention of ESRI's Address Data Management Solution. One of the tasks in the solution has you update the master street name file and then use that file to create the domain. That approach works, sort of. In addition to the domain edit limitations, I find trying to pick a valid street name from a mile long list impractical.

My thought process is if all users can edit the master street name file I'd like to run a verification against a new centerline street geometry insert such that the name entered on the new street is already in the master street name file. If it is, great, if not return some sort of warning to the effect of 'Hey there, your new street name isn't in the master streets file' which could mean the new street name was misspelled or simply has not been added.

At any rate, your suggestions are exactly what I was hoping to get, and I'll get after it as soon as I get back to the office in the morning.

Thanks again!

JoeBorgione

hehehe... closer to 1.5, but who's counting?!

danretired

Don't rush it... you will be split in 2

JoeBorgione

Looked at that; in theory, each of the specific values in the table are already distinct; no repeats. I'm having a hard time just understanding the logic in Arcade since I've never even dabbled in java script. For example, I don't even understand how arcade knows what the value is of $layer....

Distinct($layer, 'Status')<SPAN class="line-numbers-rows"><SPAN>‍</SPAN></SPAN>

If you ever want to get at all my personal info, (social security # banks etc) my universal password is cantwaittoretire ....

danretired

Distinct.... in Data Functions

probably with a bunch of other fluff around it

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.