Select to view content in your preferred language

arcgis pro Import domain keeps failling

1123
4
Jump to solution
07-12-2022 03:58 AM
Sietse_de_Haan
New Contributor III

Hi there,

I am trying to import a domain list in Pro 3.0 using a .csv file. The only time that I succeed is when I use numbers as code and the species of trees as description. When I use Table to Domain I only get a domain that us usable for a Long fieldtype. I created a table first in the database before using the tool table to domain. When I dont do this, so straight table to domain, I get this same errormessage.

When I try to create a domain that uses the species (text) as code, the table to domain always failes.

"ERROR 160039: The value being added to the CodedValueDomain already exists."

Even in a clean database it fails. 

What am I doing wrong? Cause I do want a text domain instead of a number domain. I have attached the .csv that I use.

 

Hope to hear from you. 

 

Sietse de Haan
https://www.linkedin.com/in/sietse-h-de-haan/
0 Kudos
2 Solutions

Accepted Solutions
RhettZufelt
MVP Notable Contributor

It is failing because you have "Meidoorn" listed twice and "Beverboom" listed three times in your table.  So, the second time it finds one of them, "already exists".

 

R_

View solution in original post

RhettZufelt
MVP Notable Contributor

This was an easy one as I've been there myself more than once.

Since you included the .csv, easy to open in Excel, pivot table with count flagged the issues.

R_

View solution in original post

4 Replies
RhettZufelt
MVP Notable Contributor

It is failing because you have "Meidoorn" listed twice and "Beverboom" listed three times in your table.  So, the second time it finds one of them, "already exists".

 

R_

Sietse_de_Haan
New Contributor III

Ooh **bleep**, you are right haha. Thanks, Ill remove the dubicates and try again.. I feel like a noob now :')  

 

cheers mate! @RhettZufelt 

Sietse de Haan
https://www.linkedin.com/in/sietse-h-de-haan/
0 Kudos
RhettZufelt
MVP Notable Contributor

This was an easy one as I've been there myself more than once.

Since you included the .csv, easy to open in Excel, pivot table with count flagged the issues.

R_

Sietse_de_Haan
New Contributor III

Havent had the time yet to try, but thanks, also for this option to check quickly in excel. Never thought about it either. Should add it to my workflow for these kind of things.

Sietse de Haan
https://www.linkedin.com/in/sietse-h-de-haan/
0 Kudos