siyuan-note/siyuan · error

number value is missing

Error message

number value is missing

What it means

normalizeNewItemTemplateValue for KeyTypeNumber requires value.Number != nil — the Number sub-struct holds the numeric content and its format. A Static-mode value on a Number column that omits the Number pointer is rejected.

Source

Thrown at kernel/av/new_item_template.go:366

	if 0 == len(fieldValues) {
		itemTemplate.FieldValues = nil
	} else {
		itemTemplate.FieldValues = fieldValues
	}
	return nil
}

func normalizeNewItemTemplateValue(value *Value, key *Key) (*Value, error) {
	value = value.Clone()
	switch key.Type {
	case KeyTypeText:
		if nil == value.Text {
			return nil, errors.New("text value is missing")
		}
		value.Number, value.Date, value.MSelect, value.URL, value.Email, value.Phone, value.MAsset, value.Checkbox, value.Relation = nil, nil, nil, nil, nil, nil, nil, nil, nil
	case KeyTypeNumber:
		if nil == value.Number {
			return nil, errors.New("number value is missing")
		}
		value.Text, value.Date, value.MSelect, value.URL, value.Email, value.Phone, value.MAsset, value.Checkbox, value.Relation = nil, nil, nil, nil, nil, nil, nil, nil, nil
	case KeyTypeDate:
		if nil == value.Date {
			return nil, errors.New("date value is missing")
		}
		value.Text, value.Number, value.MSelect, value.URL, value.Email, value.Phone, value.MAsset, value.Checkbox, value.Relation = nil, nil, nil, nil, nil, nil, nil, nil, nil
	case KeyTypeSelect, KeyTypeMSelect:
		var selections []*ValueSelect
		for _, selection := range value.MSelect {
			if nil != selection && "" != strings.TrimSpace(selection.Content) {
				selections = append(selections, selection)
			}
		}
		if KeyTypeSelect == key.Type && 1 < len(selections) {
			selections = selections[:1]
		}
		value.MSelect = selections

View on GitHub (pinned to 251596fc0d)

Solutions

  1. Set Value.Number = &av.ValueNumber{Content: <float64>, Format: ...} when key.Type is KeyTypeNumber.
  2. Ensure the sub-pointer matches key.Type exactly.
  3. Validate shape client-side before submit.

Example fix

// before
&av.Value{}  // key.Type == KeyTypeNumber
// after
&av.Value{Number: &av.ValueNumber{Content: 42}}
Defensive patterns

Strategy: type-guard

Validate before calling

if key.Type == av.KeyTypeNumber && value.Number == nil {
    value.Number = &av.ValueNumber{Content: 0}
}

Type guard

func hasNumberValue(v *av.Value) bool { return v != nil && v.Number != nil }

Prevention

When it happens

Trigger: Static mode on a Number column but Value.Number is nil; client sent &av.Value{} with no Number sub-pointer; type mismatch in an import.

Common situations: Partial Value from a client that populated a different sub-field; column-type change after template authoring.

Related errors


AI-assisted analysis of siyuan-note/siyuan@251596fc0d (2026-08-12). Data as JSON: /api/errors/67b3d740707ddb9b. Report an issue: GitHub.