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; } } }

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

Craig_Eissler_Iceman

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!

Find more posts tagged with

Accepted answers

All comments

Craig_Eissler_Iceman

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.

BrentRogan

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

Craig_Eissler_Iceman

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

B_Etter

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

nadja

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?

Craig_Eissler_Iceman

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

nadja

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?

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

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