Latest Contributions by DavidSolari

Like Dan said, Dissolve with the "sector" field should be enough. If you need a more specific workflow, here's an arcpy function that'll condense a bunch of geometries into one multipart: import ujson def reduce_geoms(geoms: list[arcpy.Geometry]) -> arcpy.Geometry: iter_geom = iter(geoms) first = next(iter_geom) assert first.type != "point" retval = ujson.loads(first.JSON) has_curves = "curvePaths" in retval path_key = "curvePaths" if has_curves else "paths" for g in iter_geom: gson = ujson.loads(g.JSON) paths = None if "curvePaths" in gson: paths = gson["curvePaths"] if not has_curves: retval["curvePaths"] = retval["paths"] del retval["paths"] path_key = "curvePaths" else: paths = retval["paths"] retval[path_key].extend(paths) return arcpy.AsShape(retval, True) ... View more

Unless it's hidden somewhere sneaky Arcade doesn't have any regex related functions, and that's all you have access to with the new Form specification. You'll either have to swap to Survey123 which does have more complex expression parsing or you can use Arcade functions like Find to see if a certain character appears in an answer or compare its location to another one. ... View more

I know if you have access to full Attribute Rules you can return a complex object to update multiple fields in a single rule, might be worth trying with the form designer (or submit an Idea if it doesn't work). ... View more

Thanks Dan! There's some good info on how to prep the Export tool and the suggestion to use the Multi-Task Road Extractor model type. Unfortunately this has the usual blog post issue where many inputs aren't explained and it also neglects to mention how to prepare the polylines. Are these long features that are diced up along the training chip boundaries or were individual features drawn over individual chips? Will the tool dice my inputs for me? ... View more

The cache format between the tools you run locally and the server are usually identical, at least if your Pro and Enterprise versions are close enough. Try building a cache for a small area on the server, then build the full cache locally. You can open most cache package formats with 7-zip and compare the file structure to what's in your server directories, if this is a new service with nothing to lose then swap the files and see if everything works as intended. This probably isn't a supported workflow so I can't guarantee anything but I do this with vector tile packages when the server rebuilds randomly fail and it works like a charm (Pro 3.1, Enterprise 11.1). ... View more

I'm virtually certain Outbox surveys only exist on the device and there's no trace on any server, a side-effect of the offline first design ESRI picked for the field app. If you have form elements that don't work offline (such as a search query for live choice updates) you might be able to correlate service hits with field activity to get rough ideas of what hasn't been submitted but this is incredibly vague at best. I've run into this with my own projects and the only solution here is to tie crew performance to finalized submissions. ... View more

Looks like the whole share toolbar is greyed out, do you see your name and org at the top-right of Pro (in the title bar, next to the notification bell)? You can use the little menu in that spot to sign in or swap to another portal, that might enable all your publishing options. ... View more

If you create a feature class that has Z coordinates and then append your data in, you can set the Z height from the start depths using arcpy. This big post should kick you off in the right direction, just remember that a positive depth is a negative Z value, and you might have to set starting Z values using a source of elevation if your depths are relative to ground (they probably are). Once you have that, you can subtract the start depth from the end depth to get the full depth, then use that to extrude your 3D points into accurate tubes. ... View more

Count Overlapping Features can also generate a table linking every input buffer to the final overlaps. You can use that table to find which overlaps relate to which buffers and ensure you're only summing up the appropriate polygons. ... View more

Now that Tasks are integrated into Field Maps this might work better for you. The tasks and plots are completely separate items and Field Maps will present different workflows and attributes for both. The tasks are stored in their own feature layer so you can create maps and dashboards just for the task features that your dispatchers can work with. ... View more

If these are attribute rules added to the feature classes and table, you can use the new Triggering Fields option to only run rules for the appropriate fields. If you're building your rules in the form view (or you're stuck on an older version of Pro) you can put a guard at the start of the expression to return early if the relevant fields haven't changed, like: if ($feature.field1 == $originalfeature.field1) return That said, a "calculate on submit" option would be handy for forms with complex rules. I doubt there'll be an option for online maps to only use cached values as the results are less predictable than offline maps, but deferring calculations doesn't have that problem. ... View more

I'm going to assume their data has variable-length arrays and this will fail at best and obliterate their original data at worst. I also can't find any built-in tools that will explode records based on a given format so I'm pretty sure this requires a trip to arcpy. ... View more

If you make a parameter a table of fields to string values and then make it dependent on the appropriate parameter you can get a pretty functional interface:   ... View more