Attribute transfer tool does not consistently save attribute mappings between session

[SandraLuken]

ArcGIS Desktop 10.0 SP3

Love the attribute transfer tool, except when it does not save my attribute mappings between ArcMap sessions. The unfortunate part is that the attribute mappings might save in a particular map document several times, but then it will stop saving the mappings so they need to be recreated each time the document is opened. Starting with a new document or different data does not help either. With potentially a large number of unique mappings (so auto-match does not help) this can be very time consuming.

Originally I thought this was due to broken data sources in the map document, but this does not appear to be the consistent reason for the attribute mappings to disappear.

Any others experiencing in consistent behaviour with the attribute transfer tool?

Thank you,
Sandra

[SandraLuken]

Thanks to Esri Canada again for helping with the detective work on this issue.

Broken links in the mxd will contribute to the attribute mappings disappearing from the document. Unfortunately even though the broken links and mappings are repaired, the mappings will never work again in the current document. You'll need to create a new document to have the attribute mappings persist between sessions.

Another Best practice - ensure that the document in use was created with the same release of software being used (in our case, some documents were created with ArcGIS 9.2).

Sandra

[DavidLok]

Each time user needs to create new mxd document (not renaming it to a new document) in order to keep the attribute transfer mapping setting means that users cannot recycle the already setup mxd to work with other data set. This requires lot of effort and time to setup the mxd in some case, and this is not a effective solution.

For example, a user can recycles the mxd by repairing the data source making it very powerful to working on different data set with same symobology  etc. The proposed way to create a brand new mxd document in order to keep attribute transfer mapping setting is not a practical and effective way because it means that user needs to re-setup all symobology, or have the symobology settings transfer to the new mxd document and this is tedious.

If the issue is about missing or mismatch link pointing to the attribute transfer mapping setting file, ESRI can create user interface allowing to update such link in the recycled MXD - just the same way as user can update the data source link. This would be great if possible.

[JenniferDooley1]

Hi All,

I've run into this behavior as well.  We are running ArcGIS Desktop 10, SP4.  In our case, the MXD was created in 10 originally.  There were never any broken data links that had to be repaired.  Is there a NIM / bug number anywhere for this issue?

Thanks!

Jennifer Dooley
Moulton Niguel Water District
Laguna Hills, CA