nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

ERROR 160091: The existing domain type does not match that of the updated domain. Failed to execute Add Join.

JaniceBaird

I get this error in Pro, ModelBuilder. I am not doing anything with domains. I can successfully create a Join in my map and then drag the Add Join from history into modelbuilder. I remove the join in the map and run the join in modelbuilder. This error comes up and I have no idea what it is about. Has anyone else seen this behavior? If I leave Pro and restart it, this error may or may not go away. There is no reason for this.

Thanks,

Janice.

Encuentra más publicaciones etiquetadas con

Accepted answers

All comments

JayantaPoddar

Did you try adding a fresh Add Join tool from the Geoprocessing pane, rather than from History?

Robert_LeClair

Are both feature classes in the same geodatabase? If not, copy the feature class from its folder into the geodatabase where the other feature class is and redo the Add Join. What is the result?

JaniceBaird

I have tried recreating the join from tools and also from history. This seems to be an intermittent error and just a scratch on the surface of many issues with ModelBuilder.

JaniceBaird

The feature classes that I am using are from different locations. One is in the FGDB for the project and the other is from our Enterprise GDB. The problem is intermittent and I have not run into it today. I am having many more issues with ModelBuilder and am not impressed! I am giving up on this for now.

Thanks for the suggestion!

Janice

JaniceBaird

I decided to export my models to python and run there. The values in the Models I created were continually changing and the Models would fail. I have to admit that this is really the first time I tried using Modelbuilder in PRO and I am totally underwhelmed! I would get the models working and then the next day I would try them again and they would fail some where. I would try to fix them but could not keep up with the failures! Having the code in python is much more reliable.

mmetzcar

Thanks for this tip. I was having the same error described in this post using Join Field from the Geoprocessing tab (not model builder), and starting from a fresh instance of the tool rather than double-clicking it in my history resolved the issue for me. I suspect the issue with the History version of my tool is because I had gone back to the source table and changed the data type from String to Long because otherwise my join was only bringing in Null values, so it must be caching something to do with the join field's type in the history of the tool and using a fresh instance of the tool means that cached information isn't referenced.

CherieBryant

Having the exact same problem. Worked fine last week, now it's not. This was a simple process so thought I'd try Model Builder, but as others suggested, I will just go back to Python.

Únete a la Conversación

Los miembros registrados pueden publicar, seguir actualizaciones y más. ¿Nuevo aquí? Regístrate gratis.

Enlaces Rápidos

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.