Describe the bug
When creating a type-bind field in submission-forms.xml in the same step as the dc.type field, it works correctly for Item Collections, but it does not work for Publication Entity Collections.
However, if the type-bind field is placed in a different step from dc.type, it works correctly for both Item and Publication Entity Collections.
To Reproduce
Steps to reproduce the behavior:
- Add a type-bound field to submission-forms.xml in the same step as dc.type.
- Submit an item to a regular (Item) Collection — the field behaves correctly.
- Submit an item to a Publication Entity Collection — the field does not behave as expected.
- Move the type-bound field to another step (different from the one containing dc.type).
- Try again — the field now works for both types of collections.
Expected behavior
The type-bind field should work for Publication Entity Collections even when placed in the same step as the dc.type field, just as it does for Item Collections.
Describe the bug
When creating a type-bind field in submission-forms.xml in the same step as the dc.type field, it works correctly for Item Collections, but it does not work for Publication Entity Collections.
However, if the type-bind field is placed in a different step from dc.type, it works correctly for both Item and Publication Entity Collections.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The type-bind field should work for Publication Entity Collections even when placed in the same step as the dc.type field, just as it does for Item Collections.