We found this issue after upgrading Magnolia from 5.4.4 to 5.4.7.

Steps to reproduce:
1. Create a content app and add a multi-value field(with composite field as value) with MultiValueSubChildrenNodePropertiesTransformer, similar with this example in Magnolia document.
2. Add a multi-value field(with simple string as value) with DelegatingMultiValueFieldTransformer. This field must be registered after the above field to reproduce the issue.
3. Run the content app and create a node with some values
4. Open the node just created and the second field's value is not shown.
5. If the first field is removed from content app definition, the second field's value could be shown