XDT error codes split into two namespaces, and recognising which one fired tells you where the bug lives before you have read a single line of the offending file. xbrldie:* codes are instance-level errors: something about the data, the contexts, or the facts is wrong. xbrldte:* codes are DTS-level errors: something about the linkbases, the schema, or the dimensional wiring is wrong. The "i" stands for instance; the "t" stands for taxonomy. One letter, very different fix.
The two most frequent xbrldie: codes are old friends. PrimaryItemDimensionallyInvalidError says a fact's dimensional context does not match what its hypercube allows: too many dimensions, too few, the wrong members, or the right members in the wrong container. DefaultValueUsedInInstanceError says a context emitted the default member of a dimension explicitly when XDT requires it to be implicit. Both are about how the instance speaks the dimensional language declared by the taxonomy.
The two most frequent xbrldte: codes shift the lens. HasHypercubeMissingContextElementAttributeError says a has-hypercube arc forgot the mandatory contextElement attribute; the linkbase author broke the cube. TooManyDefaultMembersError says two dimension-default arcs point at different members of the same dimension; the taxonomy contradicts itself.
Triage in this order. When you see xbrldie:*, open the instance and ask three questions. Are the dimensional members in the correct container (segment or scenario, per the cube's declared contextElement)? Are all the required dimensions present and only the required dimensions? Is any default member emitted explicitly? More than half of wild-caught xbrldie: errors trace to one of those three.
When you see xbrldte:*, open the linkbase. Look at the has-hypercube arc, look at the dimension-default arcs, look for missing or duplicated attributes. The instance is innocent here.
A rule that needs underlining: do not silence dimensional errors by deleting the offending fact. If a fact is dimensionally invalid, it is telling you the underlying classification is wrong. Fix the dimensional context, fix the cube, or fix the concept choice. Hiding errors in regulated reporting is how filings get rejected on second-line review.
xbrldie:* codes are instance-level dimensional errors. Most common: xbrldie:PrimaryItemDimensionallyInvalidError (fact violates its hypercube), xbrldie:DefaultValueUsedInInstanceError (default emitted explicitly).
xbrldte:* codes are DTS-level errors. Most common: xbrldte:HasHypercubeMissingContextElementAttributeError (missing contextElement on the has-hypercube arc), xbrldte:TooManyDefaultMembersError.
When you see xbrldie:* the bug is in the instance: a context, a fact, or an explicitMember. When you see xbrldte:* the bug is in the linkbase or schema: a missing attribute, a duplicated default, an inconsistent arcrole.
Always check segment versus scenario placement first when chasing dimensional errors. Half of the wild-caught xbrldie:* errors trace to wrong-container placement.
Do not silence dimensional errors by removing the offending fact. If a fact is dimensionally invalid, the underlying classification is wrong; fix the dimensional context, the hypercube, or the concept choice.
3 questions. Druk op 1 tot 4 om te kiezen, Enter om te bevestigen.
Door deze quiz af te ronden, markeer je deze sectie als voltooid.
Tip: kies met 1 tot en met 4 en bevestig met Enter.