We encountered a scenario where a batch client extension imported Object Definitions with fields referencing a Picklist (ListTypeDefinition) that didn’t exist in the target environment. The data wrote to the database successfully, but when Objects Admin tries to load, ObjectFieldDTOConverter hits a NullPointerException on the missing ListTypeDefinition reference — returning a 500 and rendering the entire Objects Admin screen as a blank page with a loading spinner.
There’s no error message, no indication of what’s wrong, and no way to fix it through the UI. We had to use the headless API to manually track down and delete the faulty objects. Restart, redeploy, and reindex did nothing since the underlying data inconsistency was not fixed.
What I’d like to see improved:
Clearer error descriptions either from the UI or in the logs. And for the Admin UI to show the actual error instead of becoming inaccessible.