Latest Contributions by DavidSolari

The FeatureSetByName function is your friend for getting data from other feature classes. As for updating another feature class from your rule, this help page explains the structure of the special object you have to return. ... View more

A few suggestions: Add some transparency to the symbols so you can see overlaps and get accurate counts Use symbols that are offset from the center, like those pushpins you suggested or a crescent moon or something. This makes it easier to see overlaps while keeping a natural appearance Play around with Clustering. This isn't a magic bullet as it can cause issues with some apps and the special aggregate popups but it's a surefire way to avoid overlaps. ... View more

If you need to store the original data between edits, you'll need an extra field to log that with one rule, then use another rule to retrieve it later. If it's all happening in the span of the same edit, you can usually just return without a value and the attribute rule won't edit anything. ... View more

I hopped in the Arcade playground and used this modified code: // Fetches features from a public portal item var evtsummary = FeatureSetByPortalItem( Portal("https://www.arcgis.com"), // portal item id "6200db0b80de4341ae8ee2b62d606e67", 0, // layer id ["*"], // fields to include false // include or exclude geometry ); var sql = "OBJECTID < 10" var related_data = Filter(evtsummary, sql); var cnt = Count(related_data); var evtlist = [] Console(cnt) if (cnt > 0) { for (var feat in related_data){ Console(Text(feat)) Push(evtlist,feat.BUILDINGID) } return Concatenate(evtlist,"\n") } else { return "-" } and I was unable to replicate your issue. What's your SQL query? If you apply the same query to the table directly in Pro or the map viewer do you get distinct rows back? If that leads nowhere, you might be pulling evtsummary in an odd way that leads to duplicates. If you can't get anywhere you might have to contact your support to see if they can replicate this with your data and Enterprise/Pro versions. ... View more

Does declaring @next_oid as "int" rather than "bigint" change anything? ... View more

I tried replicating this with the default "Point Notes" layer template and the following code but what I get is the expected behaviour: nulls pass but empty strings fail with arcpy.da.UpdateCursor('Point Notes', "Name") as cur: for row in cur: if row[0] is None and row[0] != "": print(f"[{row[0]}] passed") else: print(f"[{row[0]}] failed") >>>[None] passed >>>[] failed As you'd expect, it doesn't matter what the right hand expression is or what data's in the field, because the None check fails and stops the condition outright. All I can suggest is taking a closer look at your data or how that field index dict is constructed, I can't figure out why this is happening from the context provided. ... View more

Almost there, we just need to extract the attribute value from the feature returned by First: var sLineDiam = First(Intersects(FilterBySubtypeCode(FeatureSetByName($datastore, "WaterLine", ["DIAMETER"], true), 2), $feature)); return sLineDiam["DIAMETER"] == $feature.FITTING_SIZE Just like JavaScript (and many other programming languages) the "==" operator compares both sides and returns true if they're equivalent or false otherwise. This means you can skip the if/else block as we're returning true/false directly. If you still get errors, check to see if a Select by Location between the two feature classes works as intended in Pro, you might have features that appear to be coincident but actually aren't. ... View more

Comparing 3.5 to 3.4 in detail, I don't see any new restrictions, there's just more clarifications for why you can't run the tool on EGDB or Feature Dataset classes (as well as workarounds). @AustinStreetman if you try to define projections for some troublesome data using just the tool interface (no arcpy) do you get a better error message? ... View more

The result of Intersects is a feature set of all intersecting features, if you know there's only 1 intersecting feature you can use the First function to quickly grab a feature. You also have to grab a field from the feature for the comparison, and I think passing false for the geometry parameter in FeatureSetByName will cause problems. Therefore: var tap = First(Intersects(FilterBySubtypeCode(FeatureSetByName($datastore, "WaterLine", ["DIAMETER"], true), 2), $feature)); return tap.tapSize == $feature.FITTING_SIZE I haven't tested this but it should get you going in the right direction. ... View more

Handling date field out of the box would be great, but if not his is another good use case for this other idea for Arcade expressions in the map series options. Right now the workaround is to calculate some fields and use those to drive the map series, which is a pain to maintain if you're constantly tweaking or rerendering a layout. ... View more