Select to view content in your preferred language

Merge model builder does not preserve Field Map setting

3286
13
10-07-2021 08:44 PM
LucileFayolle
Emerging Contributor

ArcGIS 2.8.3

In my model builder I use the merge tool with the field map to reconciliate the fields of the two data source. Problem is: When I set the field map, validate by clicking ok and reopen the tool, if I click to change anything in the tool, the field map reset. Even if I change the output field name, the field map reset.

It look exactly like the bug that happened with the Append tool in 2019 (See post about it and esri answer)

I wonder if it is a common issue or it may be related to my model. I consider using the Append tool to replace this or even some Calculate field, but would rather keep the Merge.

 

Thank you

Tags (1)
13 Replies
EApolinar
Emerging Contributor

This is very interesting, however it does not seem to work for me. 

Im using the Field Map for the Append tool in a Model on ArcGIS Pro 3.1.0 and can't find a way for it to remember the Field Mapping. Everytime I close the tool/variable, it goes back to blanc. 

 

EApolinar_0-1728653530927.png

 

0 Kudos
RachelPinkston2
New Contributor

I'm still on Pro 3.2.2, I have not upgraded to 3.4.x yet, so I'm not sure if this issue has been fixed in the more recent updates, but I wanted to share that ManP's solution above, worked for me.  Creating a field map variable retains the field mapping between sessions.  Thanks. 

AFangman
Occasional Contributor

3.2.2 here. I have the same issue with the Merge not remembering my Field Map setup.

0 Kudos
CMorneau
Occasional Contributor

Hello to All.  Our team upgraded to Pro 3.4.3 on all our workstations about a month or so ago.  I tested my model that had the Merge tool Field Map issue, & it works fine now.  My settings persist from session to session, as they did once before.  I brought this issue to the attention of Esri's Shitij Mehta at the UC last year & she agreed that it sounded like a bug.  She said that she & her team would look into it.  I believe I saw somewhere that the bug was documented.  Bottom line - Esri appears to have fixed the issue.

Always great to connect with the right person at the UC & then see the issue ultimately get resolved after having that type of interaction.  Shitij is one of my Esri heroes & I always make it a point to tell her so.  Good for a few laughs, anyway.  Good luck with your models that have the Merge tool.  Please chime in if upgrading to Pro 3.4.3 resolved your issue.