Faulty Metadata Blocks do not trigger Database Rollback

What steps does it take to reproduce the issue?

1. Load an invalid Metadata Block (like this one due to our custom field type).
2. Watch the logs and the response to document the error.
3. Look at the loaded metadata fields and see some of them still being applied.

When does this issue occur?
During Metadata Customization.

Which page(s) does it occurs on?
Admin API

What happens?
The changes to the database from any fields that are valid are not rolled back.

To whom does it occur (all users, curators, superusers)?
Sysadmin

What did you expect to happen?
I would expect that any changes that may have been done are rolled back. The database transaction should be undone, so you are always in a consistent state.

Which version of Dataverse are you using?
6.8 / develop

Any related open or closed issues to this bug report?

• #9628
• #2551

Are you thinking about creating a pull request for this issue?
Maybe.

Start by reproducing the invalid Metadata Block through the Admin API during Metadata Customization, using the linked example and related issues #9628 and #2551. Trace the database transaction handling around the failed metadata import and verify that all changes from partially valid fields are rolled back, leaving the database consistent.