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

Coded values show up not description

jaykapalczynski

I created a FC and added Domains to it. I coded them as such

0 Fallen tree

1 Water Backup

When I go into Collector App and bring up the webmap then user starts to edit

Th edit window shows the symbology for each of the selections BUT it shows the 0 and 1 and not the description.

This also appears in the web map while editing....

How do I get the description to show up

Trouver plus de publications taguées avec

Accepted answers

jaykapalczynski

With help of another employee here....figured out the root of the problem....So we figured out a way to fix it early enough that we do not have to update the JSON file after it has been published to ArcGIS Server.

It turns out that when you create a Feature Class with domains the Feature Template table (?) is not updated with teh domain values. If you start and stop an edit session on that Feature Class in ArcMap before you publish the Template tables are updated with the Description from the Domain.

So Create Feature Class
Create and update fields with the Domain options
Start Edit session (you don have to edit anything or add anything, simply start the edit session )
End Edit session
Publish to ArcGIS Server

This fixed the issue for us....if you have any questions please ask....hope that I explained this well enough.

All comments

RandyBurton

I've run into the same issue, as have others. My workaround is posted in this thread: Domains do not appear in Collector after updating in AGOL. It involves correcting the types section of the layer's json file. The id should be the coded value and the name should be the description. Hope this helps.

jaykapalczynski

OK I read the other post and I am sort of following.

1. How and where do I get the jSON file from my ArcServer Map Service (Data is served up locally to AGOL)

2. I assume I would have to do this each time I republish the Map Service from my mxd, for instance if there is a schema change etc.

3. I didn't read in there what you were actually changing in the jSON file...Think you mentioned updated via the Rest API...how do I do this

Thanks for your thoughts and help

RandyBurton

I use AGOL, so the navigation might be a little different with Server.

I log into my account and go to the Content section and select the Feature Layer in question.

On the Overview tab, in the Layer's section, click on the layer name (or click the Service URL).

Near the top of the next page, there will be a link for the JSON that will take you to the json data. With AGOL it looks like this:

Rest Services

Near the bottom of the json, there is a section called types. You should see something like:

&nbsp; "types" : [
&nbsp;&nbsp;&nbsp; {
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; "id" : "0", 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; "name" : "0", 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; "domains" : 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; {
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; "FieldName" : {"type" : "inherited"} 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; }, 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; "templates" : [
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; {
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; "name" : "0", 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; "description" : "", 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; "drawingTool" : "esriFeatureEditToolPoint", 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; "prototype" : {
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; "attributes" : {
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; "FieldName" : "0"
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; }
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; }
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; }
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ]
&nbsp;&nbsp;&nbsp; }, 
&nbsp;&nbsp;&nbsp; {
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; "id" : "1", 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; "name" : "1", 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; "domains" : 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; {
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; "FieldName" : {"type" : "inherited"} 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; }, 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; "templates" : [
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; {
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; "name" : "1", 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; "description" : "", 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; "drawingTool" : "esriFeatureEditToolPoint", 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; "prototype" : {
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; "attributes" : {
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; "FieldName" : "1"
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; }
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; }
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; }
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ]
&nbsp;&nbsp;&nbsp; },
&nbsp;&nbsp;&nbsp; {
&nbsp;&nbsp;&nbsp; ... etc ...
&nbsp;&nbsp;&nbsp; } 
&nbsp; ],<SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN>

You can copy the section and edit it in something like notepad. You will need to add the description where it says 'name' (lines 4, 11, 24, 31, etc.) to the file by replacing the code value like this:

&nbsp; "types" : [
&nbsp;&nbsp;&nbsp; {
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; "id" : "0", 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; "name" : "Fallen tree", 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; "domains" : 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; {
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; "FieldName" : {"type" : "inherited"} 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; }, 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; "templates" : [
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; {
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; "name" : "Fallen tree", 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; "description" : "", 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; "drawingTool" : "esriFeatureEditToolPoint", 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; "prototype" : {
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; "attributes" : {
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; "FieldName" : "0"
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; }
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; }
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; }
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ]
&nbsp;&nbsp;&nbsp; }, 
&nbsp;&nbsp;&nbsp; {
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; "id" : "1", 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; "name" : "Water Backup", 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; "domains" : 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; {
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; "FieldName" : {"type" : "inherited"} 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; }, 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; "templates" : [
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; {
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; "name" : "Water Backup", 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; "description" : "", 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; "drawingTool" : "esriFeatureEditToolPoint", 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; "prototype" : {
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; "attributes" : {
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; "FieldName" : "1"
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; }
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; }
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; }
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ]
&nbsp;&nbsp;&nbsp; },
&nbsp;&nbsp;&nbsp; {
&nbsp;&nbsp;&nbsp; ... etc ...
&nbsp;&nbsp;&nbsp; } 
&nbsp; ],<SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN>

Start the whole types section with an opening { and drop the comma after the last square bracket and close with a }. Check it for valid json with jsonlint.com. If it checks, you can go into the admin section and update the json file.

For AGOL the admin address looks something like ('admin' between rest and services):

https : // services.arcgis.com/<xxxyyyzzz>/arcgis/rest/admin/services/<feature>/FeatureServer/0

I would practice this on a test copy of your feature and have a backup copy of your feature until you are comfortable with the process. Let me know if you have additional questions.

I have also reported this issue to ESRI. Perhaps they will have a better solution.

jaykapalczynski

In ArcGIS Server Manager I was able to click here to see the JSON

I can identify the area that needs to be updated. "name": "0";

<SPAN class="punctuation token">,</SPAN>
 <SPAN class="string token">"types"</SPAN><SPAN class="punctuation token">:</SPAN> <SPAN class="punctuation token">[</SPAN>
&nbsp; <SPAN class="punctuation token">{</SPAN>
&nbsp;&nbsp; <SPAN class="string token">"id"</SPAN><SPAN class="punctuation token">:</SPAN> <SPAN class="string token">"0"</SPAN><SPAN class="punctuation token">,</SPAN>
&nbsp;&nbsp; <SPAN class="string token">"name"</SPAN><SPAN class="punctuation token">:</SPAN> <SPAN class="string token">"0"</SPAN><SPAN class="punctuation token">,</SPAN>
&nbsp;&nbsp; <SPAN class="string token">"domains"</SPAN><SPAN class="punctuation token">:</SPAN> <SPAN class="punctuation token">{</SPAN>
&nbsp;&nbsp;&nbsp; <SPAN class="string token">"PubPriv"</SPAN><SPAN class="punctuation token">:</SPAN> <SPAN class="punctuation token">{</SPAN><SPAN class="string token">"type"</SPAN><SPAN class="punctuation token">:</SPAN> <SPAN class="string token">"inherited"</SPAN><SPAN class="punctuation token">}</SPAN><SPAN class="punctuation token">,</SPAN>
&nbsp;&nbsp;&nbsp; <SPAN class="string token">"Item"</SPAN><SPAN class="punctuation token">:</SPAN> <SPAN class="punctuation token">{</SPAN><SPAN class="string token">"type"</SPAN><SPAN class="punctuation token">:</SPAN> <SPAN class="string token">"inherited"</SPAN><SPAN class="punctuation token">}</SPAN>
&nbsp;&nbsp; <SPAN class="punctuation token">}</SPAN><SPAN class="punctuation token">,</SPAN>
&nbsp;&nbsp; <SPAN class="string token">"templates"</SPAN><SPAN class="punctuation token">:</SPAN> <SPAN class="punctuation token">[</SPAN>
&nbsp;&nbsp;&nbsp; <SPAN class="punctuation token">{</SPAN>
&nbsp;&nbsp;&nbsp;&nbsp; <SPAN class="string token">"name"</SPAN><SPAN class="punctuation token">:</SPAN> <SPAN class="string token">"0"</SPAN><SPAN class="punctuation token">,</SPAN>
&nbsp;&nbsp;&nbsp;&nbsp; <SPAN class="string token">"description"</SPAN><SPAN class="punctuation token">:</SPAN> <SPAN class="string token">""</SPAN><SPAN class="punctuation token">,</SPAN>
&nbsp;&nbsp;&nbsp;&nbsp; <SPAN class="string token">"prototype"</SPAN><SPAN class="punctuation token">:</SPAN> <SPAN class="punctuation token">{</SPAN>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <SPAN class="string token">"attributes"</SPAN><SPAN class="punctuation token">:</SPAN> <SPAN class="punctuation token">{</SPAN>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <SPAN class="string token">"Comments"</SPAN><SPAN class="punctuation token">:</SPAN> <SPAN class="keyword token">null</SPAN><SPAN class="punctuation token">,</SPAN>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <SPAN class="string token">"Case_"</SPAN><SPAN class="punctuation token">:</SPAN> <SPAN class="keyword token">null</SPAN><SPAN class="punctuation token">,</SPAN>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <SPAN class="string token">"PubPriv"</SPAN><SPAN class="punctuation token">:</SPAN> <SPAN class="keyword token">null</SPAN><SPAN class="punctuation token">,</SPAN>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <SPAN class="string token">"Item"</SPAN><SPAN class="punctuation token">:</SPAN> <SPAN class="string token">"0"</SPAN>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <SPAN class="punctuation token">}</SPAN>
&nbsp;&nbsp;&nbsp;&nbsp; <SPAN class="punctuation token">}</SPAN><SPAN class="punctuation token">,</SPAN>
&nbsp;&nbsp;&nbsp;&nbsp; <SPAN class="string token">"drawingTool"</SPAN><SPAN class="punctuation token">:</SPAN> <SPAN class="string token">"esriFeatureEditToolPoint"</SPAN>
&nbsp;&nbsp;&nbsp; <SPAN class="punctuation token">}</SPAN>
&nbsp;&nbsp; <SPAN class="punctuation token">]</SPAN><SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN>

QUESTIONS:

1. My question is where and how do I do this from ArcGIS Server?

2. I can see what needs to be changed but have NO idea where to physically modify the json file.

3. I assume that once I do this I will have to do this every time the service is updated/overwritten because the error in the json file is coming from the publishing to the rest endpoint

jaykapalczynski

Looks like I am not in the Administration Directory... How do I get there?

jaykapalczynski

OK I added admin to my URL to get to the admin section

Was this

http://services.arcgis.com/xyz/arcgis/rest/services/Layername/FeatureServer/0

Now this

http://services.arcgis.com/xyz/arcgis/rest/admin/services/Layername/FeatureServer/0

That gets me here

I click Update Definition and I dont get anything in the box. I assume the entire JSON would be there to make edits to

RandyBurton

For your photo of "Points of Interest (ID: 0)", what is the basic format of this page's web address? I think the admin page for this layer is where you need to be.

RandyBurton

I tend to look at the json file first because I've become used to working with it. But there are always a number of ways to do the same thing. Here's another option for you to try.

On the "Add Features" screen of your original post, there should be a manage button at the bottom of the screen. Click it.

The screen will show "Manage New Features" that will look something like this:

Manage Screen

Click the diamond to the right of each number and select Properties.

For Label, Name and Description, replace the number with the description for the number (domain code) and click done.

When you have gone through the list, click "Save Changes". This should update the layer's json file.

jaykapalczynski

That sounds great but I have no idea where you are at...I am in ArcGIS Server are you referencing AGOL?

I don see anything like you are explaining

RandyBurton

I see a Manage button just to the right of Undo and Redo. This would be on the map you created for your Collector crew. It could be that Server and AGOL are that different. I wonder if it is the permission level with the map you are working with. See: Manage feature templates where it says:

Click Manage.
You can only see this button if you're the owner of the feature layer or if you are an administrator in your organization.

Manage Button

jaykapalczynski

So Create Feature Class
Create and update fields with the Domain options
Start Edit session (you don have to edit anything or add anything, simply start the edit session )
End Edit session
Publish to ArcGIS Server

This fixed the issue for us....if you have any questions please ask....hope that I explained this well enough.

RandyBurton

A bug report has been submitted:

#BUG-000116957 [Enhancement] Services published from ArcMap to ArcGIS Online that contains a feature that is symbolized using coded domains, do not contain the domain description in ArcGIS Online.

Workaround

Create a feature template before publishing to ArcGIS Online.
Can also edit the json of the feature layer to include a description.

Rejoindre la conversation

Les membres connectés peuvent publier, suivre les mises à jour, et plus encore. Nouveau ici ? Inscrivez-vous gratuitement.

Liens rapides

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