Feature Templates Not Holding in Feature Service

3164
11
Jump to solution
11-23-2020 05:51 AM
AnneSanta_Maria1
New Contributor III

Good Morning,

We are working with the utility network and are having trouble keeping feature templates to hold between the map we are publishing from and the feature layer/service. We have feature templates created for all the layers in our initial map based on subtypes. When we publish the feature service and bring that back into ArcGIS Pro some of the templates are not holding their default values. See below.

Below is the feature template for the layer Electric Device in the initial map we publish to our portal from, the defaults are holding.

AnneSanta_Maria1_0-1606136672757.png

After publishing the service we bring the feature layer Electric Device back into a new map in ArcGIS Pro and some of the defaults in the feature template are no longer holding.  See the image of the template below.

AnneSanta_Maria1_2-1606137991111.png

If we delete all templates on the feature service layer in ArcGIS Pro and re-create the templates the defaults come back. But this should not be something we have to do for each layer every time we might need to change something. Has anyone run across this issue and have any suggestions to solutions? 

 

0 Kudos
11 Replies
tigerwoulds
Occasional Contributor III

Anyone know if this is fixed in Pro 2.9.1+? 

@Scott_Harris 

0 Kudos
Scott_Harris
Esri Regular Contributor

Hi @tigerwoulds I dug through some old emails and found where the issue I reported to the development team was tracked as [BUG-000135141 Feature templates: default values for subtypes are null in a feature service] in Esri Technical Support. Looking up that bug, I see that it was fixed in 2.8 (see this list of issues addressed here https://www.esri.com/content/dam/esrisites/en-us/media/products/arcgis-pro-issues-addressed/arcgis-p...)

If you are still reproducing in 2.8 and above, perhaps there is a difference in the issue you are seeing vs the original problem that was reported by @AnneSanta_Maria1 in this thread?

If it is indeed the same issue, my first suggestion would be to republish the service at 2.8 or 2.9, making sure the subtypes and their default values in the templates are behaving correctly before publishing.

If that's not working, my suggestion is to work with Esri Technical Support to help understand what aspect of the issue is different than the original bug.

This may or may not help: one workaround for the original bug was to delete the "bad" template that gets brought down from the service and recreate it in Pro.

-Scott