Has anyone successfully published a feature service to AGOL or Enterprise with default attributes in their feature template?

168
1
07-20-2022 07:40 AM
Labels (2)
David_Brooks
MVP Regular Contributor

Has anyone been able to publish an editable feature service to AGOL (or Enterprise), whereby the feature template applies default values that have been assigned to that feature class?

When I publish a simple Hosted Feature Service from Pro with default values in some fields, the default values aren't persisting in the feature template when I try to add points in either Map Viewer or Map Viewer Classic. Any ideas? The layer had a feature template set with the default values all locked and loaded at the point of publishing.

So the Feature Template in Pro looks like this:

David_Brooks_0-1657551933519.png

And the default values seem to be pulled through into Portal on he data itself:

David_Brooks_1-1657552035822.png

 

But in both Map Viewer and Map Viewer Classic, the feature template is blank for all the fields with the default values (the point symbol style correctly matches what was published though):

David_Brooks_2-1657552094803.png

When I Manage the template in Map Viewer Classic (as directed in the ESRI documentation for empty feature templates) the default values are also missing here.

Am I missing something?

The ESRI documentation is quite clear https://doc.arcgis.com/en/arcgis-online/manage-data/manage-feature-templates.htm

Create feature templates in ArcGIS Pro

If you publish a hosted feature layer from a project in ArcGIS Pro, define a feature template in the project. See Create a feature template in the ArcGIS Pro help for more information. The feature templates persist when you publish the feature layer and allow editing. Anyone editing the hosted feature layer can work with the feature templates you originally defined with ArcGIS Pro.

Starting to think this may be an overlooked limitation that needs an Idea posting.


David
..Maps with no limits..
1 Reply
HanliePetoors
New Contributor III

I have exactly the same problem.

I have noticed that the default values are actually applied, but they are only visible after the feature is created and the pop-up is shown or the feature is selected for editing.

So from the user's point of view, no defaults are entered, but in the background they are added. Not very user friendly.

 

 

0 Kudos