In many editing workflows, certain feature classes are designed to be created only in the context of a parent feature via a relationship.
Typical examples include:
- Addresses → Address entrances
In these cases, the child feature must always belong to a parent feature, and creating standalone features would lead to invalid or incomplete data.
Using the Editor widget in the ArcGIS Maps SDK for JavaScript 5.0, this workflow cannot be configured.
Current behavior
Assume a child layer that should only be editable through a relationship from a parent feature form.
If EditorViewModel.layerInfos.addEnabled: true:
- Associated features can be created from the parent feature form, but:
- The association elements layer also appears in the Create Features panel. Users can create standalone features from here. This can lead to invalid orphan features that are not linked to a parent.
If addEnabled: false:
- The association elements layer is completely hidden from the Editor widget.
- create associated features in the parent feature form is also no longer possible.
layerInfos.addEnabled: true overwrites enabled: false, so trying to achieve the right configuration with the enabled-parameter does not help.
Desired behavior
There should be a way to:
- hide a layer from the Create Features panel
- while still allowing creation of associated features through relationship editing in the parent feature form
Proposed enhancement
Introduce an additional configuration option in Editor.layerInfos, for example:
hideFromCreateFeaturesPanel: true
This would:
- remove the layer from the standalone Create Features UI
- still allow the layer to be edited when accessed through relationship forms
This would support common parent-child data models and help enforce data integrity by preventing the creation of orphan records while still enabling relationship-based editing workflows.
types | References | ArcGIS Maps SDK for JavaScript
