topic Re: Don't fully understand Error 160090 "A persisted domain record with the specified name does not exist" in ArcGIS Pro Questions

Don't fully understand Error 160090 "A persisted domain record with the specified name does not exist"

Craig_Eissler_Iceman — Fri, 30 Jun 2023 21:23:31 GMT

Hello, I find that Error 160090 does not provide a detailed enough Description or Solution

I'm not exactly sure what the Description, "A persisted domain record with the specified name does not exist" or the Solution which says to, "specify an existing domain" is even referring to exactly..?

I certainly know what a Domain is -- both from an attribute nd spatial perspective -- but I don't know what that has to do with anything. And, this particular case happened during a 'Join', so I have trouble relating that to the Error Msg.

Thanks for any clarifications!

Re: Don't fully understand Error 160090 "A persisted domain record with the specified name does not exist"

Craig_Eissler_Iceman — Tue, 11 Jul 2023 14:34:29 GMT

OK, so I'm replying to my own Post, because I've figured it out.

I believe that Error 160090 with regard to a "invalid Join" is not described well (it's not intuitive) in the Help documentation. See previous Post or search for this Error in the Help pages for this Error description.

During this The input table may currently be participating in another join. An input table is allowed one join at a time."

The Error is caused by adding a join to an existing join, where the Input Table was the Join Table in the existing join.

The Solution is to use the same Input Table as the existing Input Table or start a new Add Join with a different Input Table.

Re: Don't fully understand Error 160090 "A persisted domain record with the specified name does not exist"

BrentRogan — Sun, 13 Aug 2023 00:11:54 GMT

Thanks for replying to your question. I had the same problem and, like you, i couldn't understand the solution message, written by someone who new the problem and the solution, but not how to use simple words to explain it.

I removed the join, which was no longer required and the new join worked

Andrew

Re: Don't fully understand Error 160090 "A persisted domain record with the specified name does not exist"

Craig_Eissler_Iceman — Sun, 13 Aug 2023 13:35:43 GMT

Agree. I'm told that a revision of this is under consideration, so hopefully that will happen!

Re: Don't fully understand Error 160090 "A persisted domain record with the specified name does not exist"

B_Etter — Tue, 07 May 2024 21:23:14 GMT

You are an absolute legend! After 15 minutes of total frustration, I found your post. Issue resolved within seconds.

Re: Don't fully understand Error 160090 "A persisted domain record with the specified name does not exist"

nadja — Wed, 14 Jan 2026 14:58:46 GMT

https://community.esri.com/t5/arcgis-pro-ideas/error-160090-too-confusing-needs-better/idi-p/1307917 these posts seem linked. I've got the same error and frankly, I would never have guessed the cause. what's more, does anyone have a workaround?

Re: Don't fully understand Error 160090 "A persisted domain record with the specified name does not exist"

Craig_Eissler_Iceman — Wed, 14 Jan 2026 15:20:23 GMT

Yes, the Cause and Solution are described above in previous Posts.
You likely have an Invalid Join.

Re: Don't fully understand Error 160090 "A persisted domain record with the specified name does not exist"

nadja — Wed, 14 Jan 2026 16:01:09 GMT

thank you @Craig_Eissler_Iceman for your quick answer. The only thing invalid in my join is (in the eyes of esri), that I'm joining the same table to multiple attributes. it's a very small yes-no table, kind of like a domain or lookup table. I cannot use a domain, thus I have to use a join. Which is exactly what is described, as Cause. But the "solutions" described here https://pro.arcgis.com/en/pro-app/latest/tool-reference/tool-errors-and-warnings/160001-170000/tool-errors-and-warnings-160076-160100-160090.htm are no possible workarounds in my script, at least not an efficient workaround in this particular data set. Thus my question: Does anyone have a working workaround. meaning an efficient workaround how to join multiple times the same table to various features?