Latest Contributions by Robert_LeClair

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

In ArcGIS Pro, there isn’t a setting to increase the attachment thumbnail size inside the pop-up’s Attachments element. Attachments are shown as thumbnails; to view them larger you need to click the thumbnail/link to open the attachment in the default viewer.  ... 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

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). ... View more

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”). ... View more

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

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. ... View more

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. ... View more

“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. ... View more

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 ... View more