Latest Contributions by SFM_TravisBott

Thanks, @EarlMedina . Those are perfectly good workarounds and I'll use them instead.  I have a follow-up question, just out of curiosity around Esri as an organization. You work for them. You've observed the problem and acknowledge it as an issue. Why, then, is there not a more direct line to getting it fixed internally, seeing as you're part of the team? It doesn't make sense that I should now work with my administrator to open a case, wait to get a call back, maybe get assigned a competent tech, just to log a bug that sits around and is never resolved. You're asking a customer who pays for this service to spend their time helping fix the thing that, based on the company's documentation, should already work. ... View more

@JeffreyThompson2 well heck I appreciate your effort, and for coming back and trying to fill me/us in.  I'm going to go back to shaking my fist at Esri's lack of foresight.  ... View more

Did you ever find an answer for this? I was searching for the same thing and came across your post....it just doesn't have much in it.  ... View more

@jcarlson Would you have any suggestions on how to adapt this to compare what would effectively be the null part of the geometry for the non-intersecting part of feature to the intersecting part? I'm attempting this same operation on a dataset that is not wall-to-wall. The logic to handle non-intersection works fine and returns the desired value. The problem is even if a tiny part of the feature intersects a zone it brings back the value for that zone. What I would like is, if the area of non-intersection is greater than the area intersected, return the 'null' value for non-intersection. My attempt is below, where I was thinking to define it as 'if there is no intersection or if the intersected area constitutes less than half of the total area of the feature':   var overlap_amount = 0 var cdfPortal = Portal("*") var fsFHSZ = FeatureSetByPortalItem(cdfPortal, "*", 0, ['FHSZ']) var fsFHSZIntersect = Intersects(fsFHSZ, $feature) var areaFeature = Area($feature) var areaFHSZIntersect = Area(fsFHSZIntersect) if (IsEmpty(fsFHSZIntersect) || areaFHSZIntersect < areaFeature/2) { return 0 } else { for(var z in fsFHSZIntersect) { var zone = Intersection($feature, z) var zoneOverlap = Area(zone) if (zoneOverlap > overlap_amount) { overlap_amount = zoneOverlap var largest_overlap = z["FHSZ"] return largest_overlap } } }     A direct adaptation of your code has the same problem, as does the function/dictionary technique that I've attempted in a few variations:   var cdfPortal = Portal("*") var fsFHSZ = FeatureSetByPortalItem(cdfPortal, "*", 0, ['FHSZ']) var fsFHSZIntersect = Intersects(fsFHSZ, $feature) var intersected_zones = [] for(var z in fsFHSZIntersect) { var zone = { Zone: z.FHSZ, Overlap: Area(Intersection(z, $feature)) } Push(intersected_zones, zone) } function sort_by_overlap(z1, z2) { return z1.Overlap < z2.Overlap } var zone = First(Sort(intersected_zones, sort_by_overlap)) return zone.Zone if (Zone == null) { return 0 } else { return zone.Zone }     In the below image the result should be 0, but instead it brings up 'Moderate' (the area in yellow which it intersects slightly).          ... View more

@NickSchroeder I had the exact same problem with the exact same operation throwing errors in the exact same place of the exact same helper script. The slight differenced: mine was in a loop that ingested a list of jurisdictions and then creates a view for that jurisdiction. Mine worked fine in testing, and then one day it started failing but always the third time through the loop. It would create the first two just fine, run the rest of the script, and would fail at the top of iteration three.  I did not find a solution; the only thing I did was change up my test list of jurisdictions in the csv that gets ingested and then suddenly it ran through them.  I'll look forward to this thread staying perfectly quiet and neither of us ever getting an explanation.  ... View more

What a bummer. I found this thread because when I published a layer grouped like this in Pro..   I end up with this in AGOL....   And these are all coded value domains, wo when used in attempts at combination in AGOL it only reads them as the integer fields they are and reverts to arithmetic forms of aggregation.    ... View more

@JeffreyThompson2 That's actually a great idea and I hadn't considered it. Thank you for sharing.  ... View more

@JeffreyThompson2  You're right, it's possible. But it's 'possible' in the sense that it's a workaround, and far from ideal. The user experience of filtering via a list is inferior to the filter functionality that you have in dashboards. If that experience exists in dashboards, why can't it exist in experience builder? ... View more

@jcarlson I find this answer a little flat. You say "the edit widget there is meant for editing existing features and for creating singlepart geometries" as if wanting to create multipart features is somehow out of scope and presumptuous.  I ask 'why' facetiously. Of course that's a question for the developers. And I constantly wonder with Esri's products why relatively common operations, like creating multi-part features, isn't thought of when they roll things out. 'Hard to pull off' isn't really a good excuse, seeing as there's absolutely no limitation on multi part features in a feature service itself, just the widget that allows for it.      ... View more