Latest Contributions by Robert_LeClair

Try these checks—each one can cause Field Calculator / Calculate Field / Calculate Geometry Attributes to be disabled in ArcGIS Pro: Confirm the layer is editable In the Contents pane, switch to List By Editing and make sure the layer is checked (editable). Ref: Problem: The Calculate and Calculate Field options are disabled in ArcGIS Pro Make sure you’re calculating a supported field Calculate Geometry Attributes only enables for certain field types (short/long/double/float/big integer/text) and not for system fields (OBJECTID, Shape, Shape_Length, Shape_Area). Ref: Problem: The Calculate Geometry option is disabled in ArcGIS Pro Check the field isn’t set to Read Only Open the layer’s Fields view and uncheck Read Only for the target field, then Save. Ref: Problem: The Calculate Geometry option is disabled in ArcGIS Pro If it’s a feature service, don’t run Calculate Field in an edit session The geoprocessing Calculate Field tool can be blocked for feature services when you’re in an edit session / Enable Undo is on (unless using a supported branch-versioned workflow). Ref: 003307: Calculate Field is not supported against a feature service within an edit session Verify coordinate system isn’t “Unknown” If the map/dataset has an unknown coordinate system, calculate options may be disabled. Ref: Problem: The Calculate and Calculate Field options are disabled in ArcGIS Pro Repair geometry (for Calculate Geometry being disabled) Run Repair Geometry on the feature class. Ref: Problem: The Calculate Geometry option is disabled in ArcGIS Pro   ... View more

One thing to check with your Feature Drawing order workflow is NULLs.  Nulls are an exception and can make ordering look random. ... View more

Although not specific to the layout issue, in ArcGIS Pro 3.7 there's a new Analyze Map Pane you can use to troubleshoot slow layers/issues - you can read more about it here - Evaluating Your Map’s Drawing Performance: The Analyze Map Pane ... View more

Because distributed collaboration (copy) relies on the service being sync-enabled, a query layer (especially one that includes a join to a related table) generally won’t qualify—even if the underlying feature class/table have archiving—since the published dataset isn’t an archive-enabled/replica-trackable dataset in the way sync requires. That’s why you hit: “non-versioned dataset without archiving enabled by reference”. The practical workaround is to remove the runtime join from the sync-enabled layer and materialize the attributes you need for symbology/labels into the feature class that will be published. Try this - denormalize into a published “label/symbol” feature class Create a new point feature class (in your enterprise geodatabase) that includes the point geometry plus the one related record’s fields you need for labeling/symbology (or a calculated “LabelText” field). Populate it from your source using a scheduled process (geoprocessing/Python) that: joins/aggregates the related table to one row per point (since you effectively have 1:1 for this subtype), and writes/updates the point feature class fields. Enable archiving (and ensure GlobalIDs exist) on this materialized feature class (and any included tables, if applicable). Publish that layer with Enable sync, then use it in collaboration copy and for labeling. This avoids Arcade FeatureSet calls during drawing and keeps labeling fast. ... View more

What geoproce3ssing tool are you using?  Calculate Geometry Attributes or another GP tool? ... View more

This is what I have... ... View more

There is this Esri Community post here - Layer Properties Freeze ArcGIS Pro - that "may" explain what's happening. Other things to consider: Try these steps (in order). This symptom is commonly caused by a corrupted UI state/profile, GPU/WPF rendering/driver issues, or a problem layer type that makes the Properties dialog hang. 1) Reset the Pro pane/layout UI - In ArcGIS Pro: View tab → Reset Panes → Reset Panes for Mapping (Default) (or Reset Panes for Editing). 2) Do an ArcGIS Pro “soft reset” (rebuilds your Pro user profile)- this often resolves “a specific dialog/pane freezes Pro” even after reinstall, because reinstall doesn’t always clear the per-user profile.  Perform an ArcGIS pro Soft Reset 3) Rule out GPU/WPF rendering issues - Update your GPU driver (ideally from the GPU manufacturer; for laptops sometimes the laptop OEM).  If it continues, consider disabling WPF hardware rendering using Esri’s registry-key guidance (advanced). 4) Check whether it’s project-wide or layer-specific - Does it freeze on every layer (including a new shapefile/feature class in a brand-new blank project), or only certain layers (for example, very large rasters)? ... View more

This behavior is almost always due to packaging options that allow data to remain referenced (not copied)—especially for enterprise geodatabases, feature services, and UNC/network-share paths—so the recipient opens the package but has no access to the referenced source, which looks like “the data didn’t get packaged”. Project package (.ppkx): why it can arrive with no data In Pro 3.5, Project Package will only copy/extract and include enterprise/UNC/feature-service data when you package for external sharing: If Share outside of organization = unchecked (internal package), enterprise GDB layers, feature services, and UNC path data can be referenced rather than copied. If the recipient can’t reach those sources, they won’t get the data. If Share outside of organization = checked, those sources are copied/extracted and included in the .ppkx (typically extracted into file geodatabases), and connections are removed. Also: a .ppkx only includes data used in maps/scenes (items just sitting in folders/connections but not used by a layer won’t be included). Map package (.mpkx): why it may have worked for you Map packages have a similar “copy vs reference” control, but it’s a different checkbox: Include Enterprise and UNC Path Data controls whether enterprise/UNC data is copied into the .mpkx or left referenced. So it’s very possible you included data in the .mpkx (option enabled), but made an internal .ppkx (Share outside unchecked), resulting in referenced-only data that the recipient couldn’t access. Layer package (.lpkx): why it can seem inconsistent Layer packages generally include the dataset, but you can also create a schema-only layer package (no data), and some layer types have special packaging behavior. For more predictable control, Esri recommends the Package Layer geoprocessing tool. Quick checks to avoid the “no data” handoff For .ppkx to external recipients: check Share outside of organization. For .mpkx: check Include Enterprise and UNC Path Data when needed. For .lpkx: confirm it’s not schema-only; consider Package Layer GP tool for finer control. ... View more

Yes—seeing a double backslash in a registry path like C:\Program Files\ArcGIS\Pro\\Support\... is normal and typically not the cause of an install failure. No—it’s not normal for the uninstall target to point to ...\Pro\Support\ESRI.exe when that file does not exist; that usually indicates a corrupted/incomplete install/update entry. For next steps, Esri-supported troubleshooting for Pro 3.5 install/update failures - Unable to Install or Update ArcGIS pro 3.5 and Later ... View more

If I understand correctly, you may be able to use the "Use the Union and Dissolve tools" section in this tech article Fill Holes in a Polygon Feature Using Geoprocessing Tools in ArcGIS Pro - to get around the Eliminate GP tool licensing issue. ... View more

ArcGIS Pro’s direct-read Revit workflow (adding an .rvt as a BIM file workspace) doesn’t have an ArcGIS setting to “apply Revit phases” (for example, hide Demolished) the same way a Revit view/IFC export can, and it also doesn’t provide a simple “only export these parameters” switch for the BIM file workspace layers. What you can do in ArcGIS Pro instead: Filter out demolished (phase) content in ArcGIS Pro after you add the RVT: Use a Definition Query (or selections) on the relevant discipline/category layers, based on any available phase-related fields that come through from the RVT. (Field availability can vary by layer/category and authoring.) Reduce parameters only after conversion: If you convert BIM layers to a geodatabase/feature classes, you can then drop fields you don’t want (or create a “published” output with only required fields). If your goal is authoritative “what’s visible in this view / phase” export, that control is typically best handled in Revit prior to bringing it into ArcGIS (similar to what you’re seeing with IFC/view-based export). ... View more

Joined fields should be referenced in Arcade using bracket notation and the fully qualified table.field name: var a = $feature["JoinTableName.FieldA"] var b = $feature["JoinTableName.FieldB"] return a + " / " + b This is the documented syntax for joined fields in Arcade: $feature['tablename.fieldname'] (same Arcade field access rules apply). If your expression returns nothing, the most common causes are: You used $feature.JoinTableName.FieldA (dot syntax won’t work for joined fields). The join table name in the layer is not what you think (it may be an alias or auto-renamed). Use the exact qualified name shown in the layer’s attribute table fields list. The “joined” values aren’t actually present (no match in the join), so the joined field is null. Also, if you’re using a temporary/in-memory join, consider writing the join results to a new dataset (for example, run Spatial Join to create an output feature class) so the report is reading physical fields rather than a live join. ... View more