Latest Contributions by Robert_LeClair

Your filter may not be excluding what you think (spaces vs NULLs).  SHORTNAME IS NOT NULL only excludes NULL values.  It will not exclude empty spaces or strings that are just spaces.  NAME <> ' ' excludes exactly one space and will still allow an empty string, two spaces, etc.  So your source features can still pass the filter and then append blank/NULL values into the target, overwriting existing values.  Try filtering with something that excludes both NULL and "blank-ish" strings.  For example: SHORTNAME IS NOT NULL AND TRIM(SHORTNAME) <> '' or NAME IS NOT NULL AND TRIM (NAME) <> '' There is a BUG-000157944 for ArcGIS Pro that was fixed at 3.7 that may be related as well. ... View more

If the layer you’re publishing/overwriting from in Pro is a service layer (hosted feature layer / feature service / map service), that’s very likely the cause of the 003999 at Upload Service Definition. Overwrite is designed to replace a web layer based on its source dataset (file/enterprise geodatabase, etc.). When the “source” is already a service, Pro often can’t stage a valid SD to overwrite, and you end up with generic server-side failures like 003999. Best practice is to make the source a real dataset, not a service Use a FGDB or enterprise geodatabase feature class as the authoritative source in the map. Publish/overwrite the hosted feature layer from that dataset. This is the most reliable “push updates to Field Maps” pattern.   ... View more

This was answered in the ArcGIS Pro SDK community referenced here - Solved: How to add property sheet to layer's properties wi... - Esri Community (your question) ... View more

In your Python script, do you have a line that says: pdf.includeAccessibilityTags = True IncludeAccessibilityTags Property—ArcGIS Pro - it defaults to FALSE so perhaps this is why you're not seeing the tags? Also - another workflow - Solved: Automatically add PDF metadata for accessibility a... - Esri Community ... View more

Here's some information I learned from reviewing other cases: That message is coming from the Python Raster Function / deep learning model code (fastai/PyTorch), and it indicates your model (or the raster function calling it) passed an input with the wrong shape into an affine/warping step: ValueError: not enough values to unpack (expected 4, got 3) at fastai.vision.image._affine_grid means the code expected a 4D tensor size (N, C, H, W) (batch, channels, height, width) but received only 3 values (typically (C, H, W) or (H, W, C)), so it can’t proceed. The trailing message “Python Raster Function's .vectorize() method returned nothing” means the raster function’s vectorization step produced no features (often because inference failed earlier due to the shape error, or because the result was empty), so the geoprocessing tool can’t generate an output feature class/table. If this happened while running Detect Objects Using Deep Learning / similar deep learning tools in ArcGIS Pro 3.5.x, there is a related known issue where vectorization fails after the python raster function step:  BUG-000182421 for ArcGIS Pro ... View more

Here's what I learned from studying the internals: "Those dropdowns are part of ArcGIS Pro’s tool UI, not part of what a geoprocessing service can describe to clients. When you publish Focal Statistics to ArcGIS Server/Enterprise as a web tool, the service exposes parameters through the REST “GP” interface using supported server-side parameter data types. During publishing, some Pro parameter types (or composite/specialized UI controls) may be converted to simpler types (often a string), and the service metadata does not include Pro’s neighborhood “chooser” definitions—so the Server “Geoprocessing Service Directory” (and many clients) can only show a basic input box, not Pro-style dropdowns/widgets. Esri notes this generally as: some parameter data types are not supported in geoprocessing services and can be dropped or become GPString after publishing; you can verify what your parameter became by checking the task’s REST endpoint (“Task Information”). Input and output parameters—ArcGIS Pro If you want dropdown behavior for the service, you typically implement it in the client UI (web app or custom Pro add-in) and pass the correctly formatted neighborhood value to the service." Hope this helps! ... View more

I'm glad the fix worked for you!  All the best! ... View more

To add to @AJR 's comment about unique ids and not using ObjectID's, there is a workflow to configure a database sequence in this Tech Support article - Configure a Unique ID in a Feature Class That Auto-Increments by a Certain Number ... View more

Perhaps this is the underlying issue then.  Per this deprecation document - Geocoding Deprecation - it may be best going forward to rebuild the locator in ArcGIS Pro using the Create Locator GP tool to see if this makes any appreciable difference. Found this resource as well -  ArcGIS Enterprise 10.9.1 is the last release that supports publishing classic locators. ArcGIS Enterprise 11+ no longer allows publishing locators created with the classic Create Address Locator tool. Source: Deprecation: Geocoding Deprecation ... View more

Certainly - glad it worked out.  Question then as the other ones work seamlessly and this one does not, when was it created and at what release of the software?  I wonder if it's an old one that could be the case, maybe? ... View more

One thing to try is a Perform an ArcGIS pro Soft Reset - this might fix the Reconcile window issue. ... View more

G'day @TanithLives - in looking at the internals a bit more about this issue, here's some troubleshooting items to consider. Here are some steps you can try: Use Diagnostic Monitor to identify whether the slow calls are mainly ExportMapImage (map image layer draws) or query (feature layer querying). This helps pick the right mitigation. (Doc referenced in Esri KB: ArcGIS Diagnostic Monitor) If the layer is mostly for visualization, prefer cached layers (hosted tile or vector tile layers) instead of dynamic MapServer drawing. Vector/raster tiles are designed for fast display and generally perform better over higher-latency connections. (Optimize web maps, layers and apps, Manage hosted tile layers) Set visible scale ranges so layers don’t draw/query huge extents at small scales (a common cause of slow querying/drawing). (Esri Support KB 000030619) If you’re working with hosted feature layers, consider hosted feature layer views to create a “lighter” view for Pro users (different settings, potentially less content to draw/query). (Optimize web maps, layers and apps) If editing/working interactively, use Pro’s Feature Cache controls (manual fill/empty, avoid auto-cache thrash) as noted in the KB. (Esri Support KB 000030619) ... View more