Latest Contributions by Robert_LeClair

VirtualRepository.CreateClone is an internal ArcGIS Pro operation you can see in Diagnostic Monitor when Pro is cloning (copying) the layout/map state into a temporary “virtual” workspace to render/export (for example, to isolate each map series page/export so it can draw consistently). It isn’t a layer/service call itself—more like Pro preparing an internal export “snapshot.” When it suddenly becomes very slow, it’s usually because something in that export snapshot is expensive to resolve (commonly complex symbology, lots of vector content, or raster content), or you’ve hit a version-specific performance issue. There was BUG-000167349 for ArcGIS Pro that was found in 3.2.2 but fixed at 3.6 and 3.5.8 versions. You could try a flattened PDF export to see if that reduces the processing time. ... View more

Agree @MichaelVolz - I'll keep digging around. ... View more

Yes.  In the Convert Labels To Annotation (Cartography Tools) | ArcGIS Pro documentation help documenatation, it states:   - Label class scale ranges are respected. When the tool generates annotation for a specific map scale, it will only convert label classes that are turned on and visible at that scale. - If you are producing annotation at a variety of reference scales, design the map for each of those scales and avoid setting a reference scale in the map. You can then convert the labels to annotation for each scale and name them appropriately, for example, CitiesAnno_1000, CitiesAnno_100000, and so on.  I understand your disappointment.  There is an ArcGIS Idea here - ability to set different scales for different anno... - Esri Community - you can upvote so it gets some traction with the Pro Dev team. ... View more

In ArcGIS Pro, Set Data Source is intended to repoint layers to a workspace-based datasource (file GDB, enterprise GDB/SDE, folder, etc.). A Portal hosted feature layer is a web layer item, so it often won’t behave like a selectable “datasource” in that dialog—leading to what you’re seeing (OK becomes Open, and opening the item shows “this container is empty”). One workflow to consider is in the Catalog Pane, browse to the hosted feature layer and add it to the current map.  Then reapply the symbology from the "old layer" to the "new layer" using the Apply Symbology from Layer command.  Finally, remove the "old layer" and save your project. ... View more

Convert Labels To Annotation is working as designed here: it only converts label classes that are turned on and visible at the conversion scale. So at 1:8500, only your 1:6001–1:9000 label class is eligible to be converted; the other 4 classes are out of scale and won’t generate annotation.  What you could do is run the "Convert Labels to Annotation" GP tool once per scale range with the name of each FC identified by the scale.  I have not worked with the Tiled Labels To Annotation (Cartography Tools) | ArcGIS Pro documentation GP tool but it may be worth looking into as well. ... View more

That purple border is the chart view focus/active selection indicator in ArcGIS Pro (it’s not a “chart border” formatting setting), so there isn’t an option in the Chart Properties pane to turn it off. A workflows to consider so the purple border doesn't show.  Click a different view/pane first (for example, click your Map tab or the Contents pane) to remove focus from the chart, then try Export -> Capture To Clipboard again. ... View more

An easy way to do this is: 1.  Duplicate the layer in the Contents Pane 2.  For the newly created copy that is above the existing layer, create a Definition Query Genus='Stump' 3.  Symbolize the top layer with your desired "stump" symbol. 4.  Keep the original layer below, symbolized by planting season.   I "think" this would work.  Question - do you need the stump symbol to be a single symbol or by season year as well? ... View more

Since it seems that the shapefile is "somewhat" working in ArcGIS Pro, a few things I would try before exporting to a geodatabase. Recover a Corrupt Shapefile (ignor the ArcMap stuff in the document but run the Check Geometry and Repair Geometry GP tools and retry the export) From CoPilot - "The warning is generic and does not list the failed records directly — instead, it points to a file containing the full list of Object IDs of the records that could not be processed ." The file it's throwing an error message for is G-Manhole-20255.fid.  Open that file in notepad/wordpad and review the ObjectsID's / FID's.  Are there missing or strange ID's? ... View more

I think this may be related to BUG-000131663 for ArcGIS Pro - try the workaround in the link and see if that addresses the wavy line issue. If not, then try this.  If the callout (or anything underneath it) uses transparency, export a Flattened PDF (Share > Export Layout > Flattened PDF) to remove transparency tiling artifacts. ... View more

Or this workaround would work too -  Overlay the header with a manual multi-line text box (layout-only) Layout: Insert > Graphics and Text > Rectangle text Place it over the header; set background to white to hide the original header text ... View more

Likely so - converting to graphics will allow you to do a multi-line header but you then the Table Frame loses the connection to the data. ... View more

ArcGIS Pro table frames currently do not support word-wrapping column (field) headings into multiple lines—headings are drawn as single-line text, so long headings force wider columns. Here are some workarounds you can try: - Shorten the header text by changing the field alias (this affects the source layer/table). - If you need custom multi-line headers, Convert To Graphics and then edit the header text manually (note: this breaks the dynamic link so future data changes won’t update automatically). Can Table Frame Headers Be Changed without Altering the Field Aliases in an ArcGIS pro Lay ... View more

No—ArcGIS Pro does not currently provide a built-in way to limit who can use Mark As Exception in the Error Inspector pane (for topology errors or attribute rule errors) based on a role (admin/supervisor vs editor). What Mark As Exception does is update the stored error feature’s isException value (True/1), and Clear Exception sets it back to False/0: Manage attribute rule errors—ArcGIS Pro. Practical workaround: If you're working with an Enterprise geodatabase, control it with data permissions, since marking an exception is an edit to the underlying error records. If editors only have read access to the error datasets/tables, they can review errors but won’t be able to mark/clear exceptions. ... View more

Yes but.... Normally, In ArcGIS Pro > Symbology (Unique Values) you can manually add a class for a value that doesn’t currently occur in the data. Open the layer Symbology pane and set Primary symbology = Unique Values (with your Arcade expression in Field 1). On the Classes tab, click the Green Plus sign. Click the the Options dropdown, add new value.  And from here it throws an error - "requested operation could not be completed"...normally you'd go to Step 4 and be done... Click Add new value and type the value you want to symbolize (in your case, add the missing returned value, e.g. 6, and set the label to Planned). Assign the symbol you want for that class. But here's what I learned...there's a BUG.  "BUG-000161636 : Add unlisted value options triggers an error message 'Requested operation could not be completed' while adding a new value, under the symbol class using custom arcade expression." Not sure when it will be fixed as it's listed "under consideration." ... View more

There’s no current ArcGIS Online incident reported, so this is unlikely to be an AGO outage. When one sublayer in a hosted feature layer consistently fails spatial selection in both ArcGIS Pro (Select By Location) and ArcGIS Online (Find by Attributes and Location)—but works after exporting to a file geodatabase—that strongly suggests the hosted sublayer contains problem geometries (for example null/empty geometry, self-intersections, bad ring ordering, unclosed rings) and/or true curve geometry that’s not being handled as expected server-side. Try these steps: Export just the failing polygon sublayer to a file geodatabase (you’ve already proven this helps). Run Check Geometry on the exported feature class to identify bad features. Run Repair Geometry on that exported feature class (review the “Delete features with null geometry” option). If curves are involved (CAD/freehand/elliptical/Bezier), densify/convert curves before republishing. (Curves can cause issues in hosted workflows.) Overwrite/republish the hosted feature layer (or publish a clean copy) using the repaired data, then re-test the spatial selection in Pro and AGO. Retest workflow. ... View more