---
title: stack kb cases update-case-field-definition-default-space cli command
description: Update a field definition 
url: https://www.elastic.co/elastic/docs-builder/docs/4302/reference/elastic-cli/cli/stack/kb/cases/update-case-field-definition-default-space
applies_to:
  - Elastic Cloud Serverless: Preview
  - Elastic Stack: Preview
---

# stack kb cases update-case-field-definition-default-space cli command
<cli-modifiers>
</cli-modifiers>

```bash
elastic stack kb cases update-case-field-definition-default-space \
  --field-definition-id <field-definition-id> \
  --definition <definition> \
  --owner <owner> \
  [options]
```

Update a field definition

## Options

<definitions>
  <definition term="--field-definition-id string required">
    The identifier for the field definition.
  </definition>
  <definition term="--definition string required">
    The field definition as a YAML string describing a single field (type, label, control, metadata).
  </definition>
  <definition term="--owner string required">
    The application that owns this field definition.
  </definition>
  <definition term="--dry-run">
    When true, runs authorization, body, and identity-immutability validation without updating the field definition. Returns `{ "valid": true }` on success.
  </definition>
  <definition term="--description string">
    Optional human-readable description of the field's purpose.
  </definition>
  <definition term="--is-global">
    When true, this field is rendered in every case for this owner, regardless of the template used. Global fields cannot be demoted (set to false) while they are linked to an active custom field in the Cases configuration.
  </definition>
  <definition term="--name string">
    The field name, unique per owner (case-insensitive). Must match the `name` key inside the YAML definition. When omitted, the name is extracted from the definition YAML automatically. Immutable after creation. Unlike POST, the 50-character limit is not enforced on PUT so that definitions with legacy names that exceed the limit remain modifiable.
  </definition>
  <definition term="--input-file string">
    path to a JSON file to use as command input
  </definition>
  <definition term="--no-validate">
    skip input validation and send the request as-is
  </definition>
</definitions>


## Global Options

<definitions>
  <definition term="--output-fields string">
    comma-separated list of fields to include in output (dot-notation supported)
  </definition>
  <definition term="--output-template string">
    Mustache-like template for custom text output (e.g. "{{id}}: {{name}}")
  </definition>
  <definition term="--json">
    output as JSON
  </definition>
</definitions>