Tweet
We could not find this in the documentation, so I would like to ask whether EspoCRM already provides a way to inspect the field structure used by the CRM UI.
Our goal is to identify cases where a field or even an entity has already been deleted from the CRM, but references to it still remain in the UI metadata, layouts, relationships, filters, panels, or other configuration parts.
We noticed this after upgrading EspoCRM, where validation/control became stricter. Some views or windows no longer open because the UI still contains references to fields that no longer exist. In other words, the system still has “orphaned” references left behind from older customizations.
What we are looking for is something like:
If such functionality does not exist yet, I think it could be very useful as a system consistency / cleanup tool, for example:
This would help keep the system clean and avoid upgrade issues caused by outdated references.
How are others solving this today?
Do you build your own scripts/tools for checking metadata consistency, or is there already a recommended approach in EspoCRM?
Our goal is to identify cases where a field or even an entity has already been deleted from the CRM, but references to it still remain in the UI metadata, layouts, relationships, filters, panels, or other configuration parts.
We noticed this after upgrading EspoCRM, where validation/control became stricter. Some views or windows no longer open because the UI still contains references to fields that no longer exist. In other words, the system still has “orphaned” references left behind from older customizations.
What we are looking for is something like:
- A way to get the structure/list of fields currently used by the UI.
- A way to detect UI references to non-existing fields or entities.
- Possibly also a way to detect orphaned database records or metadata leftovers related to already deleted entities.
If such functionality does not exist yet, I think it could be very useful as a system consistency / cleanup tool, for example:
- detect UI references to missing fields;
- detect references to deleted entities;
- detect leftover records or metadata that are no longer valid.
This would help keep the system clean and avoid upgrade issues caused by outdated references.
How are others solving this today?
Do you build your own scripts/tools for checking metadata consistency, or is there already a recommended approach in EspoCRM?
Comment