Hi,
The error points to an issue inside the protected AdvancedAuditTrail module rather than an application document that you can fix directly.
Since you are using Advanced Audit Trail Core 3.0.2 and Advanced Audit Trail UI 3.0.2, first make sure that all AAT-related modules are on the exact same release/version. Mendix specifically recommends keeping the Core and UI modules on the same version.
I would suggest the following:
CE1707 error is still reported.I would not try to modify or delete the hidden document manually. Advanced Audit Trail is delivered as a protected module, and Mendix explicitly states that its internal implementation is intentionally hidden and should not be manually modified.
Also, Mendix 10.24.9 itself is not necessarily the problem here. AAT UI 3.0.2 is released against Studio Pro 10.21.0, so the important thing is to verify the complete dependency chain rather than only the Studio Pro version.
If the error still occurs with a fresh import of the matching AAT versions, I would raise it with Mendix Support and provide the complete dependency list and the CE1707 error. Since the failing document is protected, Support can determine whether there is a module-level compatibility issue.
Hope this helps.
Hi,
This looks like a dependency issue with the Advanced Audit Trail module. Since the error is pointing to a hidden document inside the protected AdvancedAuditTrail module, I would first check whether all AAT components are on the same version.
You mentioned Core 3.0.2 and UI 3.0.2, so those are aligned. I would also check the Dependencies of the AAT modules for any older version of AAT or one of its dependencies still being referenced.
If everything is aligned, try removing and re-importing the AAT Core and UI modules from the Marketplace, then do a clean deployment and restart Studio Pro.
I would avoid modifying or deleting the hidden document manually, since it belongs to the protected module.
If the issue still occurs in a fresh copy with the same module versions, I would suggest checking the complete dependency tree and raising it with Mendix Support, as the error may be caused by a module-level incompatibility.
Hope this helps.