topic Re: ArcGIS pro 3.0 Append in ArcGIS Pro Questions

ArcGIS pro 3.0 Append

RyanTucker — Thu, 30 Jun 2022 21:12:05 GMT

For some reason Append in the latest update, 3.0, is no longer letting me remove fields. Nor is it allowing me to set the globalID as type GUID. Anyone else having this issue?

Re: ArcGIS pro 3.0 Append

DanPatterson — Fri, 01 Jul 2022 00:19:00 GMT

Append (Data Management)—ArcGIS Pro | Documentation

What are the dialog settings? Field mapping settings?

Did you try Merge so see if it works? Although not an alternative to Append, it will provide an alternate check to validating the two data sets.

Re: ArcGIS pro 3.0 Append

LukeGilner1 — Thu, 21 Jul 2022 13:26:30 GMT

Yes, I am seeing the same thing since upgrading to 3.0. I also want to set the globalID as a GUID type, but all the properties are greyed out.

@DanPatterson this is not the case with the Merge tool. The properties are still available to adjust.

Re: ArcGIS pro 3.0 Append

RyanTucker — Thu, 21 Jul 2022 20:49:41 GMT

Same issue as Luke. Guess I'll contact tech support.

Re: ArcGIS pro 3.0 Append

RyanTucker — Wed, 27 Jul 2022 15:59:14 GMT

@LukeGilner1 Just wanted to drop a note that I had a chat with a tech analyst this morning about this issue, and he's looking into it. If I get a bug number or solution Ill let you know.

Re: ArcGIS pro 3.0 Append

RyanTucker — Thu, 28 Jul 2022 21:45:32 GMT

Just heard back from Tech support , see below:

Bug Id: BUG-000151141
Synopsis: Append tool does not allow modifying the field mapping
Status: In Review

Re: ArcGIS pro 3.0 Append

RyanTucker — Thu, 11 Aug 2022 16:23:36 GMT

Oh well according to the dev team this is "As Designed".

Someone at ESRI explain how are we to maintain globalids if we want to dump our existing data into a new empty schema if we cant change the globalID field to type guid under the append tool??

"When "use the field map to reconcile field differences" is selected in the Append tool for ArcGIS Pro 3.0, users are unable to modify the existing schema of the target dataset in the Field Map control. This is as-designed. Prior to ArcGIS Pro 3.0, the Field Map control gave the incorrect impression that fields could be added/removed and modified in the Append tool, but when the tool was actually run, these changes would not be reflected in the updated target dataset. This is because the schema of the target dataset is locked. Users are still able to specify input sources to map to target fields (i.e. reconcile field differences) that are present in the existing schema. In ArcMap the controls to add/remove fields in the Field Map for the Append tool are disabled for this same reason. The change to the Pro 3.0 Append Field Map control was done to give an accurate representation of what could be accomplished in the tool. Documentation for Pro 3.0 states that "Because the data of the input datasets is written to an existing target dataset that has a predefined schema (field definitions), the Field Map parameter does not allow fields to be added or removed from the target dataset" (https://pro.arcgis.com/en/pro-app/latest/tool-reference/data-management/append.htm). This has not changed from earlier versions of Pro. For example refer to archived 2.6 documentation at https://pro.arcgis.com/en/pro-app/2.6/tool-reference/data-management/append.htm. We will further review the documentation to ensure all tool capabilities are properly communicated. The Merge tool is recommended for combining multiple input datasets with the ability to modify existing fields.

Re: ArcGIS pro 3.0 Append

LukeGilner1 — Thu, 11 Aug 2022 16:44:16 GMT

@RyanTucker thanks for following up with this and keeping us updated.

This is frustrating! Prior to 3.0 this was a great way to maintain the GlobalID when moving data to another layer. It wasn't altering the schema at all, but allowing you to keep the GlobalID. Now the GlobalID is acting more like the useless ObjectID when trying to maintain a unique ID when moving data to a different layer.

Re: ArcGIS pro 3.0 Append

RyanTucker — Thu, 11 Aug 2022 16:54:25 GMT

@LukeGilner1

Exactly.

Now we get to go through many more steps to maintain something as simple as an attachment or relationship if we want to dump existing data with globalids into a new schema. It's beyond frustrating.

Re: ArcGIS pro 3.0 Append

JosephHilliard94 — Tue, 29 Nov 2022 14:48:41 GMT

Any update on BUG-000151141? Thanks for raising all, it's a huge pain for our team at the moment, I cannot understand why the workaround for a bug was removed.

Re: ArcGIS pro 3.0 Append

RyanTucker — Tue, 29 Nov 2022 18:14:37 GMT

ESRI Closed the bug. They claim this is how it is supposed to work. Even though prior to version 3.0 it worked the opposite way.

I escalated:

Business Justification: Then you guys need to explain HOW are we to maintain globalID's from existing datasets if we want to load the existing data into a new schema? Merge tool doesnt work for that.

No. of people affected: 1

I received no answer or explanation as to how to achieve the end goal. Typical as of late.

Re: ArcGIS pro 3.0 Append

JosephHilliard94 — Wed, 30 Nov 2022 13:48:36 GMT

Thanks for keeping us updated, frustrating, may have to stick with 2.9 for now! Definitely not as designed if they have removed a workaround for a bug!

Re: ArcGIS pro 3.0 Append

RyanTucker — Thu, 01 Dec 2022 19:02:42 GMT

@JosephHilliard94
We have a workaround! Someone dropped the workaround on another of my threads:
https://community.esri.com/t5/arcgis-pro-questions/arcgis-pro-3-0-globalid-fields-not-indexed-as/m-p/1236889#M62892

Use mobile database to append the data then convert to File geodatabase. Not pretty , but it works

Re: ArcGIS pro 3.0 Append

JosephHilliard94 — Mon, 12 Dec 2022 09:03:22 GMT

Thank you for letting me know, super helpful!