When Does the Attribute Form Service Activate?

The Attribute Form automatically opens when users perform these actions in the Studio Web App:

•edit.display-add-feature: When creating a new feature (e.g., adding a new fire hydrant to the map)

•edit.display-update-feature: When updating an existing feature (e.g., changing a pipe's material)

•edit.display-attribute-editor: When explicitly opening the attribute editor

•results.display-details: When viewing feature details from search results

•edit.display-attribute-editor-bulk - When editing several features at once (bulk editing). Available only when the selected features share the same attribute form schema.

Example: A field worker clicks on a manhole on the map. The results.display-details command triggers, and the Attribute Form displays the manhole's attributes in your customized layout.

Bulk Editing: Updating Multiple Features at Once

The Attribute Form can edit several features in a single pass. This is an alternative to the bulk editing built into Studio Web, with the advantage that edits run through your attribute form configuration - the same groups, control types, validation, coded values, catalogs, and expressions you already defined.

Under the hood, the service applies a single multi-feature update operation.

When is it available?

Bulk editing is driven by a dedicated command, edit.display-attribute-editor-bulk. The command is only active when the selected features are grouped by - and share - the same attribute form schema. If a selection mixes layers or schemas, the command stays disabled, because a single form can only represent one schema.

Scenario: A field crew replaces 12 gate valves with the same pressure rating and material. Instead of opening each valve and retyping the same values 12 times, the user selects all 12 in the result list, chooses "Edit Attributes", sets the shared values once, and submits. All 12 features are updated together.

Adding the menu item

Expose bulk editing by wiring the command to a menu item - typically in the result list context menu. Define the menu item, then reference it from the menu. The title and description point to translation keys you supply (here, language-manual-af-bulk-editing-...):

{
"id": "menuitem-edit_display-attribute-editor-bulk",
"icon": "file-multi",
"title": "language-manual-af-bulk-editing-menu-item-title",
"description": "language-manual-af-bulk-editing-menu-item-description",
"action": [
  {
    "name": "edit.display-attribute-editor-bulk",
    "arguments": {
      "attributes": {
        "slot": "top-start"
      }
    }
  }
],
"$type": "menu-item"
}

Then add it to the relevant menu (here, the result list context menu):

{
"id": "results-context",
"items": [
  "item://menu-item/zoom",
  "item://menu-item/menuitem-edit_display-attribute-editor-bulk",
  "item://menu-item/add-features-to-starred",
  "item://menu-item/remove-features-from-starred"
],
"$type": "menu"
}

How the form behaves in bulk mode

•One form is applied to many items: The form opens using the first selected feature as the template. On submit, only the attributes you changed are written to every selected feature. Fields you leave untouched are not overwritten.

•Shared vs. differing values: When all selected features share the same value for a field, that value is shown. When they differ, the field is shown empty - so you can see at a glance which attributes are uniform across the selection and which are not. Type into an empty field and that value applies to the whole selection; leave it empty and each feature keeps its own value.

•Full configuration is respected: The form renders exactly as configured. Filtered-out fields stay hidden, read-only fields stay read-only, and groups, control types, and validation behave as in single-feature editing.

•Live preview: Calculated fields, coded values, catalogs, and expressions preview as you edit, just like in single-feature mode, so you can confirm the result before applying it across the selection.