Latest Contributions by Robert_LeClair

No—there aren’t any Esri basemaps in ArcGIS Pro whose label text is keyword-searchable. Basemaps are for visualization and aren’t searchable by attributes, so you can’t search their drawn text/labels. If you need keyword search, the text must come from operational feature layers (searchable attributes) or a locator (for place-name/address search). In this tutorial below, it mentions that users can’t “search for features in the basemap” and that interactive/searchable layers should be in the operational map: Tutorial: Create an offline map—ArcGIS Pro. ... View more

GREAT!  So in my screen grab below, I have a Query widget where I created a picklist of combinations that you provided (and I'm guessing for order) where the user would pick the value of interest, then click Apply to complete the query.  Are we getting close? ... View more

So the Repair broken data links workflow in ArcGIS Pro is designed for map/scene layer and table data sources, not for project toolbox (.atbx) references. When you rename an .atbx in File Explorer, the project still points to the old filename/path, so the toolbox shows as broken—but that repair dialog won’t offer .atbx items to “repair,” so you won’t see the renamed toolbox listed. To fix it: 1. In the Catalog pane, under Project > Toolboxes, right-click the broken toolbox and Remove it. 2. Right-click Toolboxes > Add Toolbox, then browse to and add the renamed .atbx. Alternatively, rename the file back to its original name to immediately restore the reference. Repair broken data sources for layers and tables—ArcGIS Pro | Documentation ... View more

I know in ArcGIS Experience Builder, you can create a predefined unique values in a specific order for the Query widget and Select widgets.  I'm pretty sure the ArcGIS Online Map Viewer doesn't support a predefined or custom order list the way ExB does... ... View more

Is this a custom Pyton script tool by chance?  If so, then you do see the "view details" message immediately after running the tool, close out of the tool, then you go back to geoprocessing history and the "view details" tool message is gone, right?   There are some details in the following links about GP tool messages and how that works: Script tool messages | ArcGIS Pro documentation Understanding messages in script tools | ArcGIS Pro documentation ... View more

One workflow I can think of is you have two attribute fields, one call EPOCH or PERIOD where you have attribute values of MEDIEVAL, POST MEDIEVAL, IRON AGE, EARLY IRON AGE  and so.  Then another attribute field (short integer) that you field calculate where MEDIEVAL = 1 and POST MEDIEVAL = 2 and so on.  If you want the attribute table to be permanently sorted by PERIOD, then use the Sort (Data Management Tools) | ArcGIS Pro documentation to sort by attribute.  Is this what you're attempting to accomplish or am I off? ... View more

ArcGIS Pro writes GPMessages and creates the ImportLog folder in the project’s Home folder (the Home folder is also where Pro stores other “managed” project items). If you ever changed the Home folder, Pro does not move existing managed items from the old Home folder to the new one—so you can end up with GPMessages/ImportLog “outside” the folder you’re currently expecting. This is documented behavior: the Home folder “contains… geoprocessing messages” and changing it “does not move or copy” items from the previous home folder. Change current settings for a project—ArcGIS Pro Your Default Toolbox is on Microsoft OneDrive.  Esri cautions that cloud storage services such as OneDrive are not supported unless stated otherwise, which can contribute to inconsistent behavior when items are referenced from synced locations. Projects in ArcGIS Pro ... View more

What release of ArcGIS Pro are you using?  I'm using 3.6.4 and following your instructions do not see this error message. ... View more

ArcGIS Pro 3.5 can add DWG/DXF content as GIS feature layers, but it does not import an AutoCAD paper space layout/title block as an ArcGIS Pro Layout while preserving CAD layout formatting (paper space, viewports, plot styles/CTB, etc.). In Pro, CAD drawings are treated as read-only feature datasets, not layout documents: CAD data as ArcGIS Pro layers—ArcGIS Pro | Documentation ... View more

@vlabrie  - I see that you submitted an Esri Support ticket this week.  Was the analyst able to resolve this item?  Please advise. ... View more

This usually happens for one of two reasons in ArcGIS Pro: First, your line symbol needs Symbol layer drawing to keep segments “joined” and ordered at small scales. When you zoom out, Pro has to draw many more line features at once. If your symbology relies on multi-layer line symbols (for example, cased roads, stacked symbol layers, or effects that must connect across adjacent features), the appearance can change unless you explicitly control how symbol layers join/merge across features and their internal draw order.   Try these steps: Select the line layer in Contents Go to Feature Layer tab > Drawing group > Symbology In the Symbology pane, open the Symbol layer drawing tab Turn on Enable symbol layer drawing Use Join or Join and Merge (and adjust symbol class order) to maintain connectivity and the intended drawing order across segments Or reason #2 - if it's mainly wrong in the exported PDF, it may be a vector viewing/anti-aliasing artifact. Some exports look “fragmented” or appear to change when you zoom in/out in a PDF viewer because the output is vector and the viewer re-renders strokes differently at different zoom levels. You could try some of the PDF presets on the Export Map dropdown menu and see if that helps...   ... View more

This may be related to Microsoft Windows updates (notably KB5083769 and KB5082417 released in April 2026) introduce changes to file handling and SMB-related operations.  Try uninstalling both of the forementioned Windows updates by going to your Systems->Windows Updates->Update History and click Uninstall Updates.  Locate KB5083769 and/or KB5082417 and uninstall the updates.  Restart your PC and try again.  Hopefully this addresses this issue. ... View more

You’re hitting “Invalid search geometry” because your rule calls Intersects(hs, $feature) / Intersects(hs, buff) when the search geometry is sometimes null/empty/invalid (for example, the edited point has no shape yet, bad geometry, or a null geometry is being passed into Buffer()/Intersects()) Try these changes (key fixes: guard for null geometry, don’t call First() until you know there’s a result, and request only needed fields😞 // SAN POINTS QA/QC | UPDATE NETWORK ID var f = $feature.Feat_Code var o = $feature.Functn var oid = $feature.OBJECTID // ---- Guard: feature must have valid geometry ---- var g = Geometry($feature) if (g == null || IsEmpty(g)) { return null // or return $feature.NetworkID (whatever your target field is) } // HALF-SECTION // Only request the field you need; keep geometry available for distance var hs = FeatureSetByName($datastore, "HalfSection", ["HalfSec"], true) // 1) Intersect with the feature geometry (not the feature object) var interFS = Intersects(hs, g) // Container checking prevents First() on an empty set var halfSec = null if (!IsEmpty(interFS, true)) { halfSec = First(interFS).HalfSec } else { // 2) Fallback: buffer search, but only if buffer succeeds var buff = Buffer(g, 1000, "feet") if (buff != null && !IsEmpty(buff)) { var candidates = Intersects(hs, buff) var nearestHS = null var minDist = Infinity for (var feat in candidates) { var d = Distance(g, Geometry(feat)) if (d < minDist) { minDist = d nearestHS = feat } } if (nearestHS != null) { halfSec = nearestHS.HalfSec + "xy" } } } // ...continue with your decode() / network id logic... return halfSec Notes relevant to your snippet: Use Intersects(hs, Geometry($feature)) (or g) rather than Intersects(hs, $feature) to avoid type/geometry ambiguity. First(Intersects(...)) is fine only after you’ve verified the FeatureSet isn’t empty (use IsEmpty(fs, true)). If some HalfSection polygons are invalid, you can also see this error; repairing geometry on the HalfSection feature class can help. ... View more

In the ACS 5-year or Esri estimates, there is an enriched "Median Household Income" field.  In ArcGIS Pro, I also went to the Catalog Pane, clicked the Portal tab, and then clicked the ArcGIS Online cloud.  I then searched for "Median Household Income" and there were many results.  I added the "Median Household Income 2025 - Esri Demographics" web map to ArcGIS Pro.  It's very detailed.  Further, there is an ACS Median Household Income (latest) feature layer that I added to the map as well.  It does down the Census Tract level.  Not sure how it corresponds to the AMI from HUD but it's a good source to consider. ... View more

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