Subtype & Domain Does Not Publish to ArcGIS Online?

[WhiteWaterMidstream]

I use the Esri Utility & Pipeline Data Model 2018 which has alot of short integer subtypes and domains. When I publish layers to ArcGIS online I lose all of the subtype and domain definitions so when we click on features we get meaningless numbers instead of a type attribute.

Why does subtypes and domains not publish to AGOL with the layer? I'm using ArcGIS Pro to publish.

Is this a bug or oversight? Esri, can we add this to updates?

Thank you,

Lee Davis

Senior GIS Specialist

WhiteWater Midstream

[KellyGerrow]

Hello,

Publish Domains and Subtypes from ArcGIS Pro should carry over to ArcGIS Online feature services. Please get in contact with technical support to look into the specific issue in more detail to understand why this isn't carrying over for you.

Esri Support Contact Support 

-Kelly

[MikeMillerGIS · Accepted solution]

Lee,

   You need to ensure the layer uses an unique value renderer based on the subtype value. This sets the TypeID field in the feature service layers definition and ensure domains and subtypes work correctly.   

[DanielHunter]

What about AFTER the feature service is published?

My SubTypes and Domains works fine in AGOL and they work fine in Collector too.  My Problem after this is 2 fold.

1.  SubTypes and domains are NOT honored when the Feature Service is added back into a ArcGIS Pro Document.  When I try to edit web features I am unable to access domain picklists.

2.  Domains DO NOT show up in the field details, they also DO NOT show up via 'arcgis/rest/admin/services/'.

Any help is appreciated as to why this functionality seems to no be honored?

Thank you,

Dan

[mingster]

Hi Daniel,

Were you able to resolve this issue? Domains and subtypes work in AGO, but domains disappear when I try to edit the hosted feature service in Pro. The only way I can see the domains is by publishing the layer without subtypes. Thank you. 

[BrentBrady]

Hi Daniel,

Any luck with resolving this? I've got the same issue with adding AGOL content back into ArcGIS Pro and do not want to remove any subtypes.

Thanks,
Brent

[WillHouston]

Here's my experience with subtypes and domains in AGOL/Pro as of 2020-04-20:

• Subtypes and domains are added to AGOL when publishing from Pro.
• Neither subtypes nor domains will be visible when viewing that posted layer in Pro. (If you go to the domain tab, it will say something like, "Domains are read-only".)
• Neither subtypes nor Pro-style domains are easily editable in AGOL.
• Subtypes are very difficult to edit once published to AGOL because you have to use rest/admin/services and some of the data seems to be in multiple places. You can't edit them from Pro.
• The domains that are added to AGOL from Pro are different from the "Create List" domain functionality within AGOL. Adding to AGOL from Pro does not automatically create the AGOL-style domain. That means you have to edit the Pro-style domains through rest/admin/services. You can't edit them from Pro.
• Basic changes to the Pro-sourced domains in AGOL are possible through rest/admin/services. If a domain was used for multiple fields, those changes become more difficult. Pro-Based domains in AGOL are not done intelligently with the domains being a source that the fields reference. Instead, the domains and their values are copied to every field with the same name. So if you change the values for one domain and not the other, AGOL sees the same domain with different values and doesn't work.
• I haven't tested how AGOL generates lists for a field based on current values (does it read the Pro-style domain or just records the have values?).

In short, using subtypes and AGOL doesn't work well. Using domains and AGOL isn't great, but it is manageable.

Edit: Additionally, domains and subtypes for AGOL hosted feature layers that you view in Pro aren't visible when editing or viewing records.

[GabrielDeAlessio]

We are struggling with this issue.  We have multiple production datasets that rely on subtypes controlling domain lists that work in AGOL webmaps, Collector and even in ArcMap that don't work in Pro.  Rather than show the subtype controlled domains users see open text fields, which means the data being entered is a disaster.  Prior to the COVID quarantines, 99% of our data entry was done in the field using Collector.  Now users are working remotely and loading legacy data or heads up digitizing using Pro and they aren't seeing any of the domain lists.

I've gone through probably 4-6 ESRI help tickets on issues around subtypes with AGOL already.  Reaching complete exhaustion fighting subtypes.  I don't know whether to pull all subtypes (which will force a complete overhaul of large datasets and make them a LOT less efficient) or tell people to stop using Pro and go back to ArcMap (which has plenty of it's own issues when using AGOL layers) or what to do.  

[WillHouston]

I was working on a fairly new dataset for my organization, so I was able to rapidly change my data model to fit AGOL and make collection easier. The recommendation I got from my ESRI contacts was pretty simply to store what you can in AGOL and have most end users not use Pro. I changed from using the subtypes feature to a domain in AGOL, and I switched from using Collector to Survey123. Survey123 allowed me to mimic subtype domains with a choice_filter.

I don't have enough experience with ArcMap or your workflows to be of much help to you. Are there any workflows you can transition to being entirely in an AGOL map?

[deleted-user-ThzEYb7TG5Ko]

I am having a similar problem....

I have a hosted feature service with related tables that include subtypes and domains. Said subtypes and domains work when editing in AGOL and in Collector, but when opening that same table in Pro there are no domains available. This is the case both in the attributes table and the attributes tool. The only work around I can think of is getting rid of subtypes, but that would create a 70+ domain value list.... not ideal.  

If it is a stand alone table and not a feature class, is there a way to set unique value renderer? Could you explain what you mean by setting the TypeID? Do you mean setting the Field Value Type?

Did I find a bug, or am I missing something?