idea Enhance Append Tool to Allow Python/Arcade Expressions for Unmapped Fields in ArcGIS Pro Ideas

Make able the Field Mapping in all Geoprocessing tools to consume constant values

ÁkosHalmai — Sun, 26 Jun 2016 15:42:27 GMT

Make able the Field Mapping in all Geoprocessing tools to consume constant values, not just fields. In some cases for example in the Append tool in NO_TEST scenarios it would be extremely useful to fulfill a field (or multiple fields) with a constant value. There is a quite simple workaround to achieve this: leave the field unmapped and then fill it with Field Calculator. But if this feature would be integrated into the field mapping then it would be more convenient, consistent and more logical to use (raster tools can also consume constant values).

Ákos Halmai

Re: Make able the Field Mapping in all Geoprocessing tools to consume constant values

ChrisMathers1 — Fri, 15 Mar 2019 20:45:42 GMT

I was coming to create this same idea. When appending I often wish I could put in a value for a field in the target that doesn't have something to map into it.

Re: Make able the Field Mapping in all Geoprocessing tools to consume constant values

KubaSzostak1 — Sun, 04 Aug 2019 15:33:14 GMT

It would be great to see such functionality in ArcGIS Pro Append Tool.

I have about 10 shapefiles which I import into one EGD feature class. There is attribute type which I set based on shapefile name (points_fixed.shp, points_calculated.shp, points_temp.shp, ...). Having option to set Constant value would resolve my problem.

Another use case is when there is Non-NULL field in target dataset which is absent in input dataset. You can't append such data without redesigning input dataset scheme (which not always is possible).

Enhance Append Tool to Allow Python/Arcade Expressions for Unmapped Fields

feralcatcolonist_old — Tue, 26 Jul 2022 13:33:37 GMT

Enhance the Append Tool's functionality by allowing users to utilize Python or Arcade expressions to fill in output fields that do not have a 1:1 match between the two data sets.

Example:

Many exploratory data analysis feature classes start from source data with their own attribution. In the process of analysis, an individual may add/remove some fields but otherwise keep the data similar. One workflow is to then append additional records from the source data, selecting "use the field map to reconcile field differences" is useful to just add the new data, but then the user has to go into the table, highlight the newly added records and then run field calculations for each of the new columns their analysis dataset might have.

Or a different example, you have two datasets that are similar, but one is missing some relevant individualized fields-- --or has the same data in incompatible fields (it has a string and you need a numeric). You can create these fields easily enough with a field calculation expression and should be able to do this at the point of entry within the append tool.

The enhancement would look this, for a field(s) you could write in expressions to fill out the data programmatically as it uploads to your established dataset.

Re: Enhance Append Tool to Allow Python/Arcade Expressions for Unmapped Fields

RichardFairhurst — Wed, 27 Jul 2022 11:33:53 GMT

I voted for your idea and would have a use for this. Please also vote for my idea, which gives other examples of how it would be useful to be able to use Arcade for some of the parameters of other tools.

Allow Arcade Expressions in Parameters of Geoprocessing Tools

"Default Value" option for non-matched field when using Append tool

LindsayRaabe_FPCWA — Wed, 12 Apr 2023 06:28:33 GMT

When using the Append geoprocessing tool, you have the option to use the field map to reconcile field differences between the Input data and Target data.

My idea, is that when you do use this method, you have an additional option under field sources to input a default value for those fields that don't have a match. In my example below, I'm appending data from one layer with a simple Label option, into another layer that has a corresponding "Comments" fields, but also a "Class" field with 4 class options (for basic data categorisation). It would be a good time saver, if in the Class Field, I could either type in a default vale that is added against all appended features, or alternatively, select an option from the Feature Template. Obviously, it would be fine if left blank, or would not be used if a source field is mapped.

Re: "Default Value" option for non-matched field when using Append tool

Bud — Tue, 18 Apr 2023 00:47:42 GMT

Somewhat related:

In other enterprise systems like IBM Maximo, there is a concept called “Bind Variables”. Those variables can be used to get things like the system date when populating a value.

https://bportaluri.com/2012/08/variables-dynamic-queries-conditional-expressions.html
https://www.ibm.com/support/pages/username-appname-and-other-special-bind-variables-you-can-use

Would something like that be useful in ArcGIS Pro? Use the date, etc as the value for the constant/default value you’re describing? At least in some cases?

Re: "Default Value" option for non-matched field when using Append tool

LindsayRaabe_FPCWA — Wed, 12 Apr 2023 07:32:12 GMT

@Bud I could see those types of options being of value in some cases (just not in my posted example). Could even be a drop-down list of options under the Default Value, or custom value.

Append GP Tool — Use a SYSDATE constant for an unmatched field

Bud — Sat, 22 Apr 2023 00:27:17 GMT

Merged from a separate idea.

When using the Append geoprocessing tool:

We have the option to use the field map to reconcile field differences between the Input data and Target data.

It would be helpful if we had an additional option under field sources to input a system date value instead of matching a field or doing a field calculation after-the-fact.

Kind of like “Bind Variables” in other enterprise systems:

https://bportaluri.com/2012/08/variables-dynamic-queries-conditional-expressions.html
https://www.ibm.com/support/pages/username-appname-and-other-special-bind-variables-you-can-use

Could that functionality be added to the Append tool?

Re: Append GP Tool — Use a SYSDATE constant for an unmatched field

JonathanNeal — Tue, 18 Apr 2023 01:40:06 GMT

@Bud Tools support %t%, but looks like I can only make it stick to a double field, not a DateTime field.

Append GP Tool — Use SQL expression or field calculator expression to populate unmatched field

Bud — Sat, 22 Apr 2023 00:28:22 GMT

Merged from a separate idea.

When using the Append geoprocessing tool:

We have the option to use the field map to reconcile field differences between the Input data and Target data.

It would be helpful if we had an additional option under field sources to input a custom expression (SQL or field calculation) instead of matching a field or doing a field calculation after-the-fact. (It can be messy/error prone to go into the attribute table afterwards to find the new rows and do the field calculation.)

Example (SQL):

case when class='A' then 1 else 0 end

sysdate + 1

Re: Append GP Tool — Use SQL expression or field calculator expression to populate unmatched field

KoryKramer — Wed, 19 Apr 2023 14:10:50 GMT

Another flavor of https://community.esri.com/t5/arcgis-pro-ideas/enhance-append-tool-to-allow-python-arcade/idi-p/1195885

Re: Append GP Tool — Use a SYSDATE constant for an unmatched field - Status changed to: Closed

JonathanNeal — Wed, 19 Apr 2023 21:15:03 GMT

@Bud Yeah because the number is too large. Doubles and DateTimes are 64-bit and can hold a large value than the Long data type.

For trivia night, there is also %t%, %n%, and %v% (%i% is legacy replaced by %n%).

We are seeing this as a duplicate of https://community.esri.com/t5/arcgis-pro-ideas/enhance-append-tool-to-allow-python-arcade/idi-p/1195885 will link it in our internal tracking.

Our thought on how you can accomplish this now is to use the Enable Editor Tracking tool. The field will automatically generate a Creation Date Field.

Secondly, maybe you can use the Calculate Fields 3.1+ tool. We enabled a where clause that can fill in the timestamp on empty field values in a pre/post processing step?

Example input:

datetime.strptime('%t%', '%yyyy%MM%dd%HH%mm%ss')

Doc link: https://pro.arcgis.com/en/pro-app/latest/tool-reference/data-management/enable-editor-tracking.htm

Re: Append GP Tool — Use SQL expression or field calculator expression to populate unmatched field - Status changed to: Closed

JonathanNeal — Wed, 19 Apr 2023 21:15:56 GMT

@Bud Yeah good idea, will put it with the one Kory has matched:
https://community.esri.com/t5/arcgis-pro-ideas/enhance-append-tool-to-allow-python-arcade/idi-p/1195885

Re: Enhance Append Tool to Allow Python/Arcade Expressions for Unmapped Fields - Status changed to: Under Consideration

MargaretCrawford — Mon, 26 Jun 2023 18:59:13 GMT

I have marked this idea as Under Consideration because adding arcade expressions is part of our long-term plan of changes we would like to make to the field map.

Add static text option to field map in Append tool

RTPL_AU — Mon, 14 Oct 2024 00:07:54 GMT

Add the ability to enter static text as a source for a field when running the Append tool.

When using the Field Map to match source & destination fields it would be handy to be able to set a static text string as a field input.

Scenario:
I want to add the data source or the site name to a field when appending a bunch of new data sources to an existing feature class. Currently I have to bulk add a field to to all the source files and then add the source name (e.g. folder or project date) to them before appending them or I can create a new model and etc. etc.

Allow Arcade expression based field mapping in analysis tools.

cmathers — Mon, 09 Jun 2025 17:26:44 GMT

The Attribute Transfer tool exposes the global field mapping setting of the editor and allows for using Arcade expressions rather than simple mapping. It would be great if this was available in geoprocessing tools such as Append to allow the user some freedom to include a field calculation during tool execution. It would slow the tool considerably if users went overboard with it of course. You can do this already obviously with cursors in python but for the non-programmer it would be helpful.

Re: Enhance Append Tool to Allow Python/Arcade Expressions for Unmapped Fields

ChelseaRozek — Tue, 26 Aug 2025 17:43:55 GMT

Really looking forward to seeing this implemented

Re: Enhance Append Tool to Allow Python/Arcade Expressions for Unmapped Fields

HollyTorpey_LSA — Fri, 09 Jan 2026 17:50:06 GMT

This functionality would be extremely helpful. I often wish I could just calculate an unmapped value during the append process instead of having to do it in a separate step.