Latest Contributions by Robert_LeClair

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.

Sounds great @SimonSchütte_ct - to close the thread, mark whatever response you feel "resolved" the question so others can learn from this item (Accept as Solution button).

It generally does not matter for ArcGIS Pro as long as the task runs successfully. The “Configure for:” option in Windows Task Scheduler is a compatibility level for the scheduler, not an indication that ArcGIS Pro is running on/targeting that OS. That said, best practice is to change it to match the host OS (for example Windows Server 2019, or the closest available option such as Windows 10 depending on what your Task Scheduler offers). Leaving it at Windows 7 / Windows Server 2008 R2 can unnecessarily restrict some newer Task Scheduler features/options.

This behavior is almost always because the trace is still reading the old network-attribute value stored in the network topology, meaning the edit didn’t get fully incorporated by validation. Try these checks: 1. Validate the full dirty area (not just current extent)- A feature isn’t guaranteed valid “until the full extent of the feature’s dirty area is validated.” If you validate by extent and don’t fully cover the dirty area, tracing can still use outdated attribute values. 2. Confirm a dirty area is created for the attribute change - Network attributes used by tracing are stored in the topology; when the source field changes, a dirty area should be created and then validation updates the stored value used by traces. 3. If this is a Utility Network tier/subnetwork workflow - Depending on tier configuration, validation may mark subnetworks dirty and you may need follow-on QC (for example, Update Subnetwork / evaluate rules) for analytics to fully reflect changes. 4. Barrier value: code vs description - Make sure the barrier is evaluating the stored numeric value (0/1) and not a coded-value description string (“Open/Closed”).

This sounds like BUG-000183610 for ArcGIS Pro and is fixed at 3.8 From the linked BUG article, the workaround is to create a new database connection file to access the select-only layer using a different user (the issue could not be reproduced that way).

@DougBrowning - excellent! I'm glad it worked out...after 6-8 months of the mini UI boxes! All the best!

Another thing to try is Open File Explorer and navigate to C:\Program Files\ArcGIS\Pro\bin Right-click ArcGISPro.exe > Properties > Compatibility > Change high DPI settings Check Override high DPI scaling behavior, and test System or System (Enhanced) Restart Pro after each change Perhaps this will resolve the issue you're experiencing.

Great question - here's what I've been able to find out why the wizard fails for an XML file with "register data only" set for it. The Wizard is validating that the input is a Geodatabase XML workspace document (the XML format produced by Export XML Workspace Document). A replication XML created for geodatabase replication—especially when “register data only” is used—is not a workspace document (it’s a replication message/package), so the Wizard rejects it and surfaces the generic message “Invalid XML Workspace Document file provided.”

At the top left of the Elements Pane, you should see the words Map Grid with a dropdown arrow, click the dropdown arrow and select Interior Labels. This opens the Appearance for the labels. You can then expand Halo, set a Halo symbol, Color, Outline color, Outline width and Halo Size. This may accomplish what you're looking to do.

Even as a Double (64‑bit), this can still happen. Double is binary floating point, so many decimal values (including 48.3) cannot be stored exactly; Pro may show a nicely rounded display (48.3), but when you click into the edit control it can reveal the raw stored IEEE‑754 approximation, which looks like a long decimal. This is expected behavior, not something Round(field, 1) will permanently “clean up.” If your goal is “never see the long value even when editing” - Use a formatted text field for editing/display with an Arcade expression in a new field - Text($feature.DBH_OLD, "#.0") as suggested here - Solved: Decimal Places in Attribute Pane - Esri Community

Likely your numeric field type is Float and is expected behavior for float storage. One option is to the change the display formatting by opening the Fields Designer for the layer. In the Fields Designer, locate the Number Format column and double click that cell for the attribute field. Then click the 3 dots to open the Number Format pane. Change the Rounding for decimal places to 1 and then click OK. This should remove the "subatomic" number format.

“Register existing data” is not done by importing the replica XML. It’s a Create Replica option. Try these steps: 1. Pre-stage the data on the child (your target geodatabase) using a copy/paste or similiar workflow GP tool. Key requirement: the datasets on the child must already exist and match the parent (same names and schema/properties). Pro doc also notes GlobalIDs must exist before copying. 2. In ArcGIS Pro, run Create Replica (Distributed Geodatabase toolset) and check Register existing data only. You must be connected to the child geodatabase as the data owner, and the child must contain the replica datasets. About your “Invalid data” when using Import XML schema: The XML created/used for replica/disconnected workflows must be an ArcGIS-generated XML workspace document (created by Create Replica with Output Type = Xml file) and is imported with the replica/disconnected workflow (“Import data and schema”) I'd recommend reading the Help documentation Create a replica in a disconnected environment | ArcGIS Pro documentation to fully understand the process.

You can use Insert->Dynamic Text->Service Layer Credits and place it anywhere you want and style any way you wish. You can read and see more about it here - Remove Service Layer Credits ArcPro

The Clip geoprocessing tool works all license levels - Basic, Standard, Advanced according to the documentation. Since you're getting an empty output generated message, you may want to run the Repair Geometry GP tool on both feature classes to see if there are any issues with them. You did mention that the 2 FC's are in different projections - I would run the Project on the species layer to UTM NAD 83 first, then run the CLIP tool afterwards.

Re: Pop Up Elevation Profile Transects

Yes—you can export the transect path from the Elevation Profile tool to a selectable line feature class, but ArcGIS Pro does not have a built-in way to automatically show the interactive Elevation Profile graph as a pop-up when you click/select that line. To export the path to a line feature class - Interactive elevation profile | ArcGIS Pro documentation Now to make it viewable in a pop-up, you could export the profile as an image and then store it as an attachment, then configure the layer pop-up to display attachments.

Online Status	Online
Date Last Visited	20m ago

My Ideas

Latest Contributions by Robert_LeClair

Re: ArcGIS Pro Report Expression Not Reading Joined Field Correctly

Re: Import XML Replica "Register existing data"

Re: Changing OS for Scheduled Task in Task Manager?

Re: Add Network Attribute (Trace Network) Issues

Re: ArcGIS Pro 3.6+ — Adding a view-only layer disables editing on ALL other layers (regression from 3.5.2)

Re: Delete dialog box went mini on me

Re: Delete dialog box went mini on me

Re: Import XML Replica "Register existing data"

Re: Mask Graticule labels at edge of map frame?

Re: Field Length/Precision Display

Re: Field Length/Precision Display

Re: Import XML Replica "Register existing data"

Re: Service Layer Credits providing too much information

Re: Limiting a polygon to a specific boundary

Re: Pop Up Elevation Profile Transects

Re: Delete dialog box went mini on me

Re: Limit who can mark as exception in Error Inspe...

Re: Service Layer Credits providing too much infor...

Re: Create a different symbology based on an attri...

Re: Select by Location in ArcGIS Pro on a multi-la...

Esri Forestry Group (EFG)