Latest Contributions by Robert_LeClair

Thanks for the info! A non-insert (listed under Updates) should normally have a Common ancestor representation available in the Differences pane—because Pro defines Common ancestor as “the state of the feature in the current version before it was edited.” If Pro can’t retrieve that representation for a feature that’s categorized as an update, it’s typically pointing to an inconsistency in branch versioning metadata or a service/query issue, not an expected editing scenario. One known, relevant class of problems is branch versioning metadata becoming inconsistent under conditions (features may end up “referencing a moment before the common ancestor moment” or otherwise not participating correctly in version operations). Esri documents this as a workflow issue and provides guidance for reviewing branch recovery versions after upgrades here - https://support.esri.com/en-us/knowledge-base/000032501  Also, there are ArcGIS Server fixes/patches around branch queries and the “ancestor moment timestamp” being used correctly for branch requests (again, not exactly your UI symptom, but related to retrieving the correct historical representation) Now to why it might be for only one approver - perhaps it's because you’re seeing it only via the feature service, and only intermittently, two things to consider: whether Pro is intermittently failing to retrieve the ancestor representation from the service (auth/token/session/network/cache), or whether only a subset of rows has missing/incorrect branch metadata (so only certain features/versions show it). To isolate the cause, try these checks the next time you catch/see the issue. Have the approver reproduce, then immediately test the same version/feature on another machine/user.  If only one user sees it, collect their Pro version/build, Windows profile, and whether they’re using the same portal connection. Compare through a different path (service vs direct admin inspection. You can’t view/edit named branch versions via an .sde connection (only Default), but you can use an .sde connection for version administration and inspection. Check whether the feature has odd system field patterns when the issue occurs (GlobalID, editor tracking fields, etc.) and whether the “Update” might actually be a delete/insert pattern coming from your workflow (some edits can be represented that way depending on the operation). To get your approvers unstuck, here's a potential workaround - when this occurs, have them use the map pop-up / attribute table plus the Version Changes list to identify which fields the editor touched (editor tracking fields can help), since the Differences grid isn’t reliable for that record in that run. Not ideal, but it’s the fastest operational workaround. Hope this helps! ... View more

This is not something I’d consider expected behavior for a non-insert in branch versioning. In the Differences pane for branch version changes, ArcGIS Pro is intended to show three representations per feature—Current, Target, and Common ancestor. The Common ancestor is defined as “the state of the feature in the current version before it was edited.” If the feature is categorized as Update (not Insert), Pro should generally be able to show that pre-edit state so only the truly changed fields are highlighted. "Is there a valid scenario where a non-insert has no common ancestor with default?"  At a version lineage level, a “common ancestor” moment exists (it’s the last moment the version and default referenced the same state). But what you’re describing is more specific: Pro can’t retrieve/represent the feature’s ancestor state in the Differences grid, so it flags everything. That usually points to a limitation/defect or a data/state edge case (rather than a normal editing scenario). What I need to narrow this down In the Differences list, is the feature under Update, Delete, or Insert? Does this happen for all approvers / machines, or just one? Is the layer coming from the branch versioned feature service only, or can you reproduce it when connecting directly to the enterprise geodatabase branch version (not through the service)? Has Prune Branch History been run recently, or do you use replicas/offline workflows? (These can affect what historical “moments” remain available, and are called out in branch history docs as related to referenced moments and pruning.) If you answer those, I can check for known issues/KBs specific to Pro 3.5.x + Enterprise 11.3 and the Differences pane/common-ancestor display. ... View more

Try these common fixes for ERROR 999999 with Transform Route Events in ArcGIS Pro 3.6 (it’s a generic “unhandled” tool failure): Repair geometry on the routes and any feature class inputs involved, then rerun: Data Management > Features > Repair Geometry. Avoid shapefiles/CSV for inputs or outputs: export everything to a file geodatabase (FGDB) table/feature class and use those. Use a short, simple output path and name (no special characters; don’t start with a number; avoid deep folders). Test a small subset (select a few routes/events and export to a new FC/table; run the tool on that). If it works, process in chunks. Run ArcGIS Pro as Administrator to rule out permission/write issues. ... View more

There's this BUG-000177883 for ArcGIS Pro that says it was fixed at 3.7 but it does make me wonder... ... View more

Hmmm...a couple questions for you: 1.  The Map View that you're in - is it a web map or local data making the map? 2.  Maybe there's a problematic layer.  If this only happens in the one Map View, turn off layers one by one and attempt to zoom in/zoom out.  Does one layer freeze? 3.  What release of ArcGIS Pro are you using? Sometimes, a Perform an ArcGIS pro Soft Reset does the job.  ... View more

ArcGIS Pro doesn’t currently provide a control to “increase the chart canvas/margins” for a pie chart without effectively changing the pie/label layout. If labels are getting cut off, the supported approaches are to adjust the label settings instead. Try these options: In the chart’s Chart Properties pane → Slices tab → Labels, increase the Character limit (slice labels truncate by default). The full label is also available on hover.  Reduce what’s displayed in the slice labels (for example, show percentage only instead of category + value + percent). Use Grouping threshold to combine small categories into Other, which reduces label crowding.  ... View more

In full transparency, the Esri Support AI Chatbot came back with this below.  It's somewhere to start in troubleshooting your expression: Use Distinct() on a FeatureSet and pass both field names to get unique combinations of `Naziv` + `TipAlteracije`: var u = Distinct($layer, ["Naziv", "TipAlteracije"]) return u If you need it as a text list (for a report/dynamic text), concatenate the distinct rows: var u = Distinct($layer, ["Naziv", "TipAlteracije"]) var s = "" for (var r in u){ s += r.Naziv + " | " + r.TipAlteracije + TextFormatting.NewLine } return s Reference: [Arcade FeatureSet functions — Distinct](https://developers.arcgis.com/arcade/function-reference/featureset_functions) ... View more

If you don't need to run Python, then the Frequency (Analysis Tools) | ArcGIS Pro documentation will do the job easily enough. ... View more

ArcGIS Pro 3.5 generally does not recognize the Autodesk coordinate system definition stored in a DWG from AutoCAD Map/Civil 3D (including “NAD83 California Zone 5 (US Survey Feet)”). When Pro can’t detect an Esri spatial reference for a CAD dataset, it treats it as Undefined and may assume it matches the map’s coordinate system. One option to consider: Create an Esri-format projection file for your target coordinate system. Place it in the same folder as the DWG. The name must match the DWG exactly, e.g. MyPolyline.dwg MyPolyline.prj Pro will then use that PRJ to define the CAD dataset’s coordinate system. Per the documentation that Dan mentioned - "an AutoCAD file may contain coordinate system information in the DWG or DXF file created using the Esri ArcGIS for AutoCAD plug-in application, or as a result of the Export To CAD geoprocessing tool. " ... View more

Understand.  So, sadly, in ArcGIS Pro, there isn’t a built-in dynamic spatial filter that continuously re-evaluates a layer as another layer’s geometry changes (including “within a distance”).  I know one can do this running a series of GP tools to ultimately get to the updated list point of points within 10 miles of a wildfire perimeter.  Presumably one could script the workflow and schedule the Python script to execute daily via Windows Task Scheduler.  Could do the same thing in ModelBuilder too. ... View more

Okay.  So Experience Builder can do “points within a straight-line distance of polygons” using the Query widget (not the Filter widget). Here are some steps you can try: Add a Query widget and set the data source to your points layer. In the Query widget, add a Spatial filter and choose Selected features from data source (the option that returns features that have a spatial relationship with features in another layer). Add filter layer = your polygons layer. Turn on Enable buffer and set the distance and units (this is the “within a distance” part). Use the Query result (output data source) to drive what the user sees (connect your Map/List/Table widgets to the query result). You can learn more about the Query widget here - Query widget—ArcGIS Experience Builder | Documentation ... View more

Gotcha.  So question then - what type of map application will you be using?  Experience Builder?  Instant Apps?  Other? Related - straight line distance or drive time/distance? ... View more

I wonder if this workflow, Spatially Filter Feature Layers with Definition Queries, would work for you? ... View more

Question:  Are you using an Enterprise GDB or a File GDB?  For an Enterprise geodatabase you must be the data owner. To create or manage attribute rules, you must access the Attribute Rules view “from the geodatabase as the data owner.” If you connect as a user who is not the data owner, the Attribute Rules view is read-only. It’s also read-only from a web feature layer.  In addition, the Attribute Rules view is read-only when accessed with an ArcGIS Pro Basic license. ... View more