A user creates a custom metadata schema that includes a multi value text field After...

If themulti-value text fieldis being populated unexpectedly, the most likely cause is thatanother field in the metadata schema is mapped to the same property. When multiple fields are mapped to the same property in AEM, any updates to either field will overwrite or modify the property, leading to the unexpected population of values.

This can happen due to schema misconfiguration, where fields unintentionally share the same JCR property path.

Option B is incorrect because the value being required would not cause it to be populated automatically. Option C suggests simultaneous updates by different users, which is unlikely to cause the issue described.

Check themetadata schema configurationto ensure fields are mapped to distinct properties.