Display attribute dialog after storing new features

08-04-2020 11:42 AM
Status: Open
Labels (1)
Regular Contributor II

Please consider adding the "Display attribute dialog after storing new features" Editing Options feature from ArcMap into PRO.   Setting the attribute value in Templates doesn't really cut it. Configure a feature template—ArcGIS Pro | Documentation This is only a crude work-around and does not come close to an intuitive pop-up dialog that's available in ArcMap. This feature is extremely useful when creating 100s or 1000s features with many different attribute values. 


Hi Jakub,

I know you are aware of authoring a template to prompt for attributes based on the documentation link you provided, but have you tried out the Active Template when creating new features?

Enter attributes for new features—ArcGIS Pro | Documentation 

Does it help?




Thanks Scott. I did. You still have to populate the values prior the creating the feature. If you do not remove the the values the next feature you create will inherit those same values. This is prone to error. The proven approach is: display a floating window with attributes (all blank unless you have a default value in specified in the schema) immediately after a new feature is created on the layer(s) specified. This allows the user to enter the corret values after the feature has been created thus QAQC it visually as well and ensuring only new correct values are entered. 


This would also be helpful for editing workflows that involve copying and pasting features from other feature classes with differing schema.


I agree that it would be nice to be able to modify attributes prior to committing the edit, as was possible in ArcMap (shown in OP screenshot).

For my team, we have built in database validation rules that prevent the creation of new features that do not already exist in a supporting table.

Our current workflow in ArcMap, is basically: start editing session, find the location, digitize the point,  review attribute popup window, correct necessary attributes that differ from feature template defaults, add primary key, commit changes, move on.

While we can use the active template tools Scott mentioned in Pro, that would require a semantic change to our workflow.  If possible, it would certainly ease the transition for my users if they didn't have to readjust their workflows to one that's slightly less efficient.