List of Fault Corrections
This release resolves defects identified through the following support incidents
| Product / Module | Description |
|---|---|
| Administration 3.1.1 | Unable to move/delete Template items in E3D 3.1.10 Able to move/delete the same Template items in E3D 3.1.5 |
Important changes
UPDATE access mode databases:
This release resolves an issue related to claiming TMPL elements within extracts. The fix introduces an enhanced version of the Data Integrity Checker (DICE) in Administration, which updates the claim tables of databases by adding the missing entries for older TMPL elements. The absence of these entries was causing claiming failures when working with extracts.
Some time ago, TMPL elements were redefined as primary claim elements. This change was introduced to allow multiple users to work concurrently on templates under a single TMAR element in the template environment.
However, this modification had an unintended impact on existing TMPL elements already present in the model when using extracts. By making TMPL elements claimable, the extract management procedures (Claim, Flush, Issue) began expecting corresponding entries in the claim tables. Older TMPL elements—created before this definition change—do not have these entries, which leads to extract crashes when attempting to process these “old‑style” TMPLs. Typical error messages include:
(2,362) Invalid Dopelib version number (43,362) Element kerror 651
In this Administration version, the DICE patch identifies all TMPL elements that are missing entries in the claim tables and forces those entries to be created, thereby restoring the expected data integrity.
When DICE detects primary elements that lack claim‑table entries—typically because they were created using an older schema—it will report an error similar to the following.
Missing claim table entry for primary %TMPL element =123/1 in Database number: 10 Extract number: 1
|0:7
When patching these errors DICE will show a message like this.
PATCH: Inserting claim table entry for %TMPL element =123/1 in Database number: 10 Extract number: 1
|0:7
When patching an extract family, every corrupted member must be processed together in a single continuous patch operation. The patch will fail and abort if any of the corrupted members are not primary (writable) at the time the patch is executed. When DICE detects this type of corruption in a database or extract that is not primary, it will report an error of this kind.
Warning: contains x TMPL element(s) which are missing claim table entries. To fix, must be made primary at this location to run the patch.
Attempting to DICE patch without making this extract/database primary will fail with this error
Attempt to patch failed: contain x TMPL element(s) which are missing claim table entries. To fix, must be made primary at this location to run the patch.
In this scenario, the correction must propagate from the Master database through every extract level in the family as one continuous operation. It is not possible to patch this issue extract by extract; in fact, DICE will not detect this corruption when run at the extract level. Only running DICE on the Master will identify the corruption across the entire extract family and apply the necessary fix.