Domain does not update when service is republished

[ZachBodenner]

Hello,

I have a feature service which references an Enterprise gdb feature class. I created a new domain, applied it to one of the fields in the feature class, and overwrote the service (Enterprise 11.1). Despite everything saving correctly and publishing correctly, I'm not able to select from the values in the domain when I go to edit the feature in a web environment. Also, the REST endpoint does not show the coded values in the attribute info. 

This has been kind of a long running problem - sometimes a similar issue will get fixed if I overwrite a service like 10 times, and other, like now, I just can't get the changes to stick.

[Clubdebambos]

Hi all,

Just reporting a similar issue in case this solution works for someone else.

I have two services from the same feature class, one is editable for admins and the other is read-only. They are referenced from two different SDE connections (Edit/Read-only) to the same database, so they both point to the same data. With a republish, the editable version domains updated and the read-only did not. 

• I removed the domains assigned (I did not delete the domains) via the editable SDE.
• Re-published without domains.
• Re-assigned the domains to the fields.
• Published again and voila.

ArcGIS Pro 3.4.0, Enterprise 11.1.

All the best,

Glen

[ChrisWiebke]

I had this problem.  I stopped and restarted the service, then my coded values were visible in the service.

[MarkGo]

Having this same issue. Published a shared referenced service from SQL Server in Arc Pro 3.4.3 to Enterprise 11.4

Stopping and restarting the service didn't do anything at all. No domains shown in QueryDomains in the REST endpoint. Pulling the FC into Pro showed the domains just fine. Re-publishing the service multiple times had no effect.

Found this thread, and changing to a dedicated instance finally showed the domains. Once they showed up, I could change back to a shared instance, but every time there is an update to any of the domains, it has to be switched to dedicated & back. 

This is really frustrating to say the least, because for this particular service, I will need to setup a process that updates the domain nightly based on another table. This will obviously add a lot of overhead to that automation.

[Town_of_Fuquay-Varina_GIS]

I'm still on 11.1, and I just wanted to follow up and note that I also notice the same behavior when re-publishing after updating a relationship class. I republished after the changes, but it didn't update the relationship values as shown in the REST relationship details. I had to close Pro, re-open, and re-publish, and it updated after that. I'm thinking this is the same symptom as with domains where it is sometimes not passing the updated service definition values for whatever reason when things are republished.

[apericak]

On Pro 3.3 / Enterprise 11.3, I had the same problem where I couldn't see domain changes on a shared instance service until I went to dedicated, but then couldn't get those changes to stick when I switched it back to shared. In my case, though, changing the Enterprise site-level schema lock setting to disable "Lock database schema for shared instances" and then restarting the problem service resolved it for me (in that link, scroll down to the "Modify the schema lock setting for shared instance map services" section.)

Interestingly, I'm pretty sure I published the service from Pro with "Enable schema locking" turned off (Share As Web Layer --> Configuration tab --> Configure Parameters button --> Properties --> Advanced), but it seems like the site-level setting to lock the schema overrode that choice. So if your organization allows the site-level schema lock setting to be disabled for shared instances, it might be worth trying that out.