"Cannot modify definition with existing submissions"
If you try to edit a definition and see “Cannot modify definition with existing submissions”, the definition is locked. This is expected behaviour, not a bug — and there’s a safe way forward.
Why definitions lock
Section titled “Why definitions lock”A definition locks automatically as soon as at least one certificate has been created against it. From that point, DASH refuses any change that would alter the structure, including:
- editing the definition itself,
- adding, updating or deleting a property,
- changing the entity hierarchy,
- importing properties into it.
The same protection blocks deleting the definition (“Cannot delete definition with existing submissions.”) and importing into it (“Cannot import to definition with existing submissions.”).
The reason is data integrity: certificates already signed and submitted must keep referring to the exact structure they were built on. Changing it underneath them would break the record of what was certified.
What to do instead: create a new version
Section titled “What to do instead: create a new version”To change a locked definition, leave the original in place and create a new definition (a new version) with your changes:
- Create a new definition — see Create a definition. If the new one is close to the old one, import its properties as a starting point — see Import properties.
- Make your changes on the new definition while it’s still unlocked.
- Point new certificates (and the relevant definition map) at the new definition going forward.
- Keep the original definition for the certificates that already use it — do not try to force changes onto it.