XBRL Diagnostics List
These diagnostics appear when there is an error that will prevent the generation of a valid XBRL instance file. These errors must be corrected before the export can proceed.
| Error | Description | Notes |
|---|---|---|
| Context '<context name>' does not specify a valid entity. |
The specified context in the XBRL Global Settings has an invalid value for either the 'Scheme' or 'Identifier' field. These fields are used to identify an entity in XBRL. |
Clicking Correct will bring up the XBRL Contexts dialog to allow the user to correct the entity information. |
| Context '<context name>' requires the applicable period to be specified. | The specified context in the XBRL Global Settings defines a fully specified date or period but is missing a required date (either the start date, end date, or both). | Clicking Correct will bring up the XBRL Contexts dialog to allow the user to enter the missing date(s). |
| Context '<context name>' does not specify the currency to be used. | The specified context in the XBRL Global Settings defines a monetary context, but no unit of currency has been assigned. |
Clicking Correct will bring up the XBRL Contexts dialog to allow the user to select the appropriate currency. Note that this diagnostic only appears when exporting an XBRL v2.0 instance document. |
| Tuple tag has been used. | An object in the document has been tagged with a tuple element. Tuples are meant to group related sets of tags together and are not used for holding a value. | Clicking Correct will bring up the XBRL Tagging dialog with the tagged object selected to allow the user to remove the tag or select a different one. |
| Global tag is monetary however a non-monetary context ('<context name>') is used. | A global tag is using a monetary element but has been assigned the specified non-numeric context. Note that this message may also appear as a warning (see Warnings table). | Clicking Correct will bring up the XBRL Global Settings to allow the user to change the context assigned to the global tag. Note that this diagnostic only appears when exporting an XBRL v2.0 instance document. |
| Tagged information is monetary however a non-monetary context ('<context name>') is used. | An object in the document has been tagged with a monetary element but has been assigned the specified non-numeric context. Note that this message may also appear as a warning (see Warnings table). | Clicking Correct will bring up the XBRL Tagging dialog with the tagged object selected to allow the user to change the tag or assign an appropriate numeric context. Note that this diagnostic only appears when exporting an XBRL v2.0 instance document. |
| A unit of measure (currency) was not specified for monetary tag '<tag name>'. |
An object in the document has been tagged with a monetary element with the specified name, but has not been assigned a numeric unit. |
Clicking Correct will bring up the XBRL Tagging dialog with the tagged object selected to allow the user to change the tag or assign an appropriate numeric unit. |
| Global tag is numeric however a non-numeric context ('<context name>') is used. | A global tag is using a numeric element but has been assigned the specified non-numeric context. |
Clicking Correct will bring up the XBRL Global Settings to allow the user to change the context assigned to the global tag. Note that this diagnostic only appears when exporting an XBRL v2.0 instance document. |
| Tagged information is numeric however a non-numeric context ('<context name>') is used. | An object in the document has been tagged with a numeric element but has been assigned the specified non-numeric context. |
Clicking Correct will bring up the XBRL Tagging dialog with the tagged object selected to allow the user to change the tag or assign an appropriate numeric context. Note that this diagnostic only appears when exporting an XBRL v2.0 instance document. |
| Global tag is non-numeric however a monetary context ('<context name>') is used. | A global tag is using a non-numeric element but has been assigned the specified numeric context. |
Clicking Correct will bring up the XBRL Global Settings to allow the user to change the context assigned to the global tag. Note that this diagnostic only appears when exporting an XBRL v2.0 instance document. |
| Tagged information is non-numeric however a monetary context ('<context name>') is used. | An object in the document has been tagged with a non-numeric element but has been assigned the specified numeric context. |
Clicking Correct will bring up the XBRL Tagging dialog with the tagged object selected to allow the user to change the tag or assign an appropriate non-numeric context. Note that this diagnostic only appears when exporting an XBRL v2.0 instance document. |
| Tagged information is numeric however a unit of measure has not been assigned. | An object in the document has been tagged with a numeric element but has not been assigned a numeric unit. | Clicking Correct will bring up the XBRL Tagging dialog with the tagged object selected to allow the user to change the tag or assign an appropriate numeric unit. |
| Item representing information at a specific date is using a context associated with a duration. | An object in the document has been tagged with an element requiring a context representing a specific point in time, but the assigned context represents a duration of time. | Clicking Correct will bring up the XBRL Tagging dialog with the tagged object selected to allow the user to change the tag or assign an appropriate context. |
|
Item representing information over a period is using a context associated with a specific date. |
An object in the document has been tagged with an element requiring a context representing a duration of time, but the assigned context represents a specific point in time. | Clicking Correct will bring up the XBRL Tagging dialog with the tagged object selected to allow the user to change the tag or assign an appropriate context. |
| Context '<context name>' was referenced but no longer exists. | An object in the document has been tagged and assigned a context that no longer exists. |
Clicking Correct will bring up a dialog asking the user if they wish to correct the first tag using the missing context, or if they wish to modify the context list. |
| Numeric Unit '<unit name>' was referenced but no longer exists | An object in the document has been tagged and assigned a numeric unit that no longer exists. | Clicking Correct will bring up a dialog asking the user if they wish to correct the first tag using the missing unit, or if they wish to modify the numeric unit list. |
|
Multiple values for the tag '<tag name>'. |
Multiple objects in the document have been tagged with an element in the taxonomy that should only be used once. |
Clicking Correct will bring up a dialog to allow the user to choose how to resolve the multiple tagging. If resolved, a single tag will be exported with the resolved value. Note: In anticipation of this eventuality, a right-click menu has been implemented when selecting a tag with a single option 'Allow multiple tags for this item'. For known duplicate tag assignments, this option will account for this eventuality prior to running the diagnostics. |
|
Different values found in items using tag '<tag name>'. |
Multiple objects in the document have been tagged with an element in the taxonomy. This taxonomy element has been configured to export a single value only if all tagged values are equal. At least one of these values are different from the rest. If resolved, a single tag will be exported with the resolved value. If no corrections are made, all instances of the tag are exported regardless of the differing value(s). |
Clicking Correct will bring up the Goto Tag dialog. This will enable the user to choose one of the items with multiple tagging and jump to it with the XBRL Tagging dialog open. |
|
Automatic XBRL tag could not be found. |
An object in the document has been configured to be tagged automatically using mappings defined in the database but this tag’s mapping could not be found. |
Clicking Correct will bring up the XBRL Tagging dialog with the tagged object selected to allow the user to change the tagging configuration. |
|
A required tuple was not found. |
A tuple has been found that requires a certain child tuple that was not found. |
Clicking Correct will close the export and bring up the XBRL Tagging dialog with the first element of the parent tuple selected. |
|
Tagged item requires a value. |
An object in the document has been tagged but does not have a value and hence, will not be exported. However, this tag is a required element of a tuple and should contain a value so that it can be exported. |
Clicking Correct will close the export and bring up the XBRL Tagging dialog with the blank item selected. |
|
A required tag was not found. |
A tuple has been found but is missing required child elements. |
Clicking Correct will close the export and bring up the XBRL Tagging dialog with the first element of the parent tuple selected. |
|
Not enough occurrences of tag. |
A tuple has been found that contains required child elements, but at least one of those elements do not appear enough times. |
Clicking Correct will close the export and bring up the XBRL Tagging dialog with the last found instance of the missing child element selected. |
|
Not enough occurrences of tuple. |
A tuple has been found that contains some required child tuples, but there are not enough occurrences of at least one of those child tuples. |
Clicking Correct will close the export and bring up the XBRL Tagging dialog with the first element of the last found tuple instance selected. |
|
Not enough occurrences of a group of tags. |
A tuple has been found that is supposed to contain instances of a grouping of tags. However, there are not enough occurrences of at least one of those groupings. |
Clicking Correct will close the export and bring up the XBRL Tagging dialog with the first element of the last found instance of the tag grouping selected. |
|
A required grouping of tags was not found. |
A tuple has been found that is supposed to contain instances of a grouping of tags. However, at least one of those groupings was not found. |
Clicking Correct will close the export and bring up the XBRL Tagging dialog with the first element of the parent tuple selected. |
|
Tagged item's value does not match the fixed value specified by the Taxonomy. |
An object in the document has been tagged with an element requiring a specific value, but the assigned value does not match. |
Clicking Correct will bring up the XBRL Tagging dialog with the tagged object selected to allow the user to change the tag. |
|
The sum of the values from duplicate '<tag name>' items has resulted in a number too large to be represented. |
The specified tag has 'Add values together for the tag' option enabled, but the addition of all the values for this tag has resulted in a number that is too large for the system to represent. |
Clicking Correct will bring up the XBRL Tagging dialog with the tagged object selected to allow the user to change the tag or turn off the 'Add values together for the tag' feature. |
|
Taxonomy Element not found for fraction item numerator. |
An object in the document has been tagged with an element representing a fraction. These elements have two child elements, one representing the numerator, and one representing the denominator. The Taxonomy Element that is supposed to represent the numerator could not be found in the Taxonomy. This is likely an error in the Taxonomy schema. |
Clicking Correct will bring up the XBRL Tagging dialog with the tagged object selected to allow the user to change the tag. |
|
Taxonomy Element not found for fraction item denominator. |
An object in the document has been tagged with an element representing a fraction. These elements have two child elements, one representing the numerator, and one representing the denominator. The Taxonomy Element that is supposed to represent the denominator could not be found in the Taxonomy. This is likely an error in the Taxonomy schema. |
Clicking Correct will bring up the XBRL Tagging dialog with the tagged object selected to allow the user to change the tag. |
|
Tagged item's value does not correspond to the datatype of the taxonomy element. |
The value assigned to the tag did not pass the validation of the datatype specified for the taxonomy element. This might happen, for example, if you assign a string to a tag expecting a numeric value. |
Clicking Correct will bring up the XBRL Tagging dialog with the tagged object selected to allow the user to change the tag. |
|
Tagged item's value does not meet the length requirement specified for this taxonomy element |
The value assigned to the tag has a length that does not meet the 'length' constraint specified for the datatype of the taxonomy element. Note: Length has different meanings depending on the datatype of the element. For types based on XML’s 'string' or 'anyURI' types, the length is defined as the number of characters. For types based on XML’s 'hexBinary' or 'base64Binary' types, the length is defined as the number of octets of binary data. For types based on XML’s 'QName' or 'NOTATION' types, any value is valid (i.e., it ignores the length constraint). |
Clicking Correct will bring up the XBRL Tagging dialog with the tagged object selected to allow the user to change the tag. |
|
Tagged item's value does not meet the minimum length requirement specified for this taxonomy element. |
The value assigned to the tag has a length that is less than the minimum required length specified by the 'minLength' constraint for the datatype of the taxonomy element. Please see the note for the 'length' constraint above for length definitions. |
Clicking Correct will bring up the XBRL Tagging dialog with the tagged object selected to allow the user to change the tag. |
|
Tagged item's value exceeds the maximum length requirement specified for this taxonomy element. |
The value assigned to the tag has a length that exceeds the maximum length specified by the 'maxLength' constraint for the datatype of the taxonomy element. Please see the note for the 'length' constraint above for length definitions. |
Clicking Correct will bring up the XBRL Tagging dialog with the tagged object selected to allow the user to change the tag. |
|
Tagged item's value does not conform to a required pattern specified for this taxonomy element. |
The value assigned to the tag fails to conform to an XML regular expression that is specified in a 'pattern' constraint for the datatype of the taxonomy element. |
Clicking Correct will bring up the XBRL Tagging dialog with the tagged object selected to allow the user to change the tag. |
|
Tagged item's value does not match one of the enumerated values specified for this taxonomy element. |
The value assigned to the tag is not equal to one of the enumerated values specified in the datatype for the taxonomy element. |
Clicking Correct will bring up the XBRL Tagging dialog with the tagged object selected to allow the user to change the tag. |
|
Tagged item's value is greater than the (inclusive) upper bound specified for this taxonomy element. |
The value assigned to the tag is required to be less than or equal to the value specified in the 'maxInclusive' constraint for the datatype of the taxonomy element. Note: For numeric types, this constraint compares values numerically. For any of the date and time related types, this constraint compares values chronologically. |
Clicking Correct will bring up the XBRL Tagging dialog with the tagged object selected to allow the user to change the tag. |
|
Tagged item's value is greater than the (exclusive) upper bound specified for this taxonomy element. |
The value assigned to the tag is required to be strictly less than the value specified in the 'maxExclusive' constraint for the datatype of the taxonomy element. Please see the note for the 'maxInclusive' constraint above for comparison definitions. |
Clicking Correct will bring up the XBRL Tagging dialog with the tagged object selected to allow the user to change the tag. |
|
Tagged item's value is less than the (exclusive) lower bound specified for this taxonomy element. |
The value assigned to the tag is required to be strictly greater than the value specified in the 'minExclusive' constraint for the datatype of the taxonomy element. Please see the note for the 'maxInclusive' constraint above for comparison definitions. |
Clicking Correct will bring up the XBRL Tagging dialog with the tagged object selected to allow the user to change the tag. |
|
Tagged item's value is less than the (inclusive) lower bound specified for this taxonomy element. |
The value assigned to the tag is required to be greater than or equal to the value specified in the 'minInclusive' constraint for the datatype of the taxonomy element. Please see the note for the 'maxInclusive' constraint above for comparison definitions. |
Clicking Correct will bring up the XBRL Tagging dialog with the tagged object selected to allow the user to change the tag. |
|
Tagged item's value exceeds the total number of allowed digits specified for this taxonomy element. |
The value assigned to the tag cannot have more digits than the number specified in the 'totalDigits' constraint for the datatype of the taxonomy element. Note that leading zero digits or trailing fractional zero digits are not considered for the purposes of this constraint. |
Clicking Correct will bring up the XBRL Tagging dialog with the tagged object selected to allow the user to change the tag. |
|
Duplicate measures found in divide element of Numeric Unit '<unit name>'. |
The specified numeric unit in the XBRL Global Settings contains a division measure type and there is an identical unit of measure present in both the numerator and denominator. This is not allowed. |
Clicking Correct will bring up the XBRL Numeric Options to allow the user to correct the unit of measure. |
|
Invalid currency selected for Numeric Unit '<unit name>'. |
The specified numeric unit in the XBRL Global Settings specifies a monetary unit of measure, but the settings for the unit of measure do not represent a valid currency. |
Clicking Correct will bring up the XBRL Numeric Options to allow the user to correct the unit of measure. |
|
Tagged item's value exceeds the allowed number of fractional digits specified for this taxonomy element. |
The value assigned to the tag cannot have more fractional digits (i.e., digits to the right of the decimal point) than the number specified in the 'fractionDigits' constraint for the datatype of the taxonomy element. Note that trailing fractional zero digits are not considered for the purposes of this constraint. |
Clicking Correct will bring up the XBRL Tagging dialog with the tagged object selected to allow the user to change the tag. |
|
Invalid namespace used for segment defined in Context '<context name>'. |
The specified context in the XBRL Global Settings defines one or more segment elements and at least one of them is defined in the http://www.xbrl.org/2003/instance namespace or has a blank namespace, neither of which are allowed. |
Clicking Correct will bring up the XBRL Contexts to allow the user to correct the segment information. |
|
Invalid namespace used for scenario defined in Context '<context name>'. |
The specified context in the XBRL Global Settings defines one or more custom scenario elements and at least one of them is defined in the http://www.xbrl.org/2003/instance namespace or has a blank namespace, neither of which are allowed. |
Clicking Correct will bring up the XBRL Contexts to allow the user to correct the custom scenario information. |
|
Invalid measure identifier on Numeric Unit '<unit name>'. |
The specified numeric unit in the XBRL Global Settings defines a unit of measure with an invalid namespace or uses the namespace http://www.xbrl.org/2003/instance and an identifier that is not either 'shares' or 'pure'. |
Clicking Correct will bring up the XBRL Numeric Options to allow the user to correct unit of measure. |
|
Invalid unit of measure specified on Numeric Unit '<unit name>'. |
The specified numeric unit in the XBRL Global Settings does not have a valid definition for the unit of measure. |
Clicking Correct will bring up the XBRL Numeric Options to allow the user to correct unit of measure. |
|
Invalid measure namespace on Numeric Unit '<unit name>'. |
The specified numeric unit in the XBRL Global Settings does not have a valid namespace for the unit of measure. |
Clicking Correct will bring up the XBRL Numeric Options to allow the user to correct unit of measure. |
|
A monetary item is not using an ISO 4217 currency designation. |
An object in the document has been tagged with a monetary element, but has been assigned a numeric unit that does not represent one of ISO 4217 currency designations. |
Clicking Correct will bring up the XBRL Tagging dialog with the tagged object selected to allow the user to change the tag or the assigned numeric unit. |
|
An item representing shares is not using the built-in XBRL shares unit of measure. |
An object in the document has been tagged with an element that has a datatype of 'sharesItemType' or a datatype derived from it, but it has been assigned a numeric unit that does not represent the built-in XBRL 'shares' unit of measure. |
Clicking Correct will bring up the XBRL Tagging dialog with the tagged object selected to allow the user to change the tag or the assigned numeric unit. |
|
Context '<context name>' does not specify a valid period. |
The specified context in the XBRL Global Settings does not define a valid period. |
Clicking Correct will bring up the XBRL Contexts to allow the user to correct the period information. |
|
Invalid segment element '<element name>' defined in Context '<context name>'. |
The specified context in the XBRL Global Settings defines a segment element with the given name, which is invalid. |
Clicking Correct will bring up the XBRL Contexts to allow the user to correct the segment information. |
|
Invalid segment attribute '<attribute name>' defined in Context '<context name>'. |
The specified context in the XBRL Global Settings defines a segment element with an attribute having the given name, which is invalid. |
Clicking Correct will bring up the XBRL Contexts to allow the user to correct the segment information. |
|
Invalid scenario element '<element name>' defined in Context '<context name>'. |
The specified context in the XBRL Global Settings defines a custom scenario element with the given name, which is invalid. |
Clicking Correct will bring up the XBRL Contexts to allow the user to correct the custom scenario information. |
|
Invalid segment element '<element name>' defined in Context '<context name>' |
The specified context in the XBRL Global Settings defines a custom scenario element with an attribute having the given name, which is invalid. |
Clicking Correct will bring up the XBRL Contexts to allow the user to correct the custom scenario information. |
| Tagged item is referencing an invalid tuple instance | The tagged item is referencing a non-existent tuple instance with the ID displayed in the Severity box. | Clicking Correct will bring up the XBRL Tagging dialog with the tagged object selected to enable the user to change the tag. |
| Too many occurrences of <tagged item/tuple> "<tag name>" | The number of occurrences of the tag or tuple with the given name has exceeded the maximum that the parent tuple instance is allowed to contain. | Clicking Correct will bring up the XBRL Tagging dialog with the tagged object or the first item of the tuple selected to enable the user to change the tag. |
| The <tagged item/tuple> "<tag name>" could not be added to the parent tuple "<tuple name>" | A tagged item or a child tuple could not be added to its parents tuple instance. This can occur because other items in the parent are preventing it from being added without violating constraints, or if the tagged item or child tuple is not defined as a valid child of the tuple parent at all. | Clicking Correct will bring up the XBRL Tagging dialog with the tagged object or the first item of the tuple selected to enable the user to change the tag. |
| More than one value has been found for the “<dimension name>” dimension. | A context (whose name is in the Details area) has used the specified dimension more than once (e.g., once in the Scenario and once in the Segment). The XBRL Dimensions specification states that any given dimension can only be used once. | Clicking Correct will bring up the XBRL Contexts to allow the user to correct the dimensional information. |
| Default dimension value used in Context “<context name>”. | The specified context contains a dimension that has been explicitly assigned the default dimension value for that dimension (the name of the dimension and the dimension value are in the Details area), which is invalid. | Clicking Correct will bring up the XBRL Contexts to allow the user to correct the dimensional information. |
| Tagged item “<tag name>” is not dimensionally valid. | A tagged item using the specified tag is associated with a context (whose name is in the Details) that does not contain appropriate dimensional information according to the taxonomy. |
Clicking Correct will bring up the XBRL Contexts to allow the user to correct the dimensional information. Tip: To show exactly what dimensional information is required by the tagged item, right-click the tag in the XBRL Tagging dialog and select New Dimensional Context. This will bring up the Edit Dimensions dialog with the drop-downs set to display exactly all the dimensional information required by the tagged item. |
| Context “<context name>” does not reference a valid typed dimension. | The specified context indicates that there should be typed dimensional information, but the dimension being referenced (whose name is in the Details area) does not specify a valid typed dimension in the taxonomy. | Clicking Correct will bring up the XBRL Contexts to allow the user to correct the dimensional information. |
| Context “<context name>” does not reference a valid explicit dimension. | The specified context indicates that there should be explicit dimensional information, but the dimension being referenced (whose name is in the Details area) does not specify a valid explicit dimension in the taxonomy. | Clicking Correct will bring up the XBRL Contexts to allow the user to correct the dimensional information. |
| Invalid dimension value found in Context “<context name>”. | The specified context contains a dimension that references an invalid dimension value (the name of the dimension and the dimension value are in the Details area). | Clicking Correct will bring up the XBRL Contexts to allow the user to correct the dimensional information. |
| Multiple values associated with a single footnote. | A footnote (whose label and language code are shown in the Details area) is defined in the document, but multiple values have been found associated with it. For example, this may occur if 2 different paragraphs representing content for different footnotes have been linked to the same footnote in the XBRL Footnotes dialog. | At the moment, the Correct button is disabled for this diagnostic. This may be enhanced in a future version to allow the user to manually select the desired value for the footnote. For now, the export cannot continue until the user exits the XBRL Export and manually corrects the issue. |
These diagnostics warn of potential errors in the exported instance document. They will not stop the export, however they may be indicative of a semantic error somewhere in the document.
| Warning | Description | Notes |
|---|---|---|
|
At least 1 value does not sum up to its total. |
XBRL taxonomies can define a calculation linkbase, which specifies basic calculation validation rules (e.g., the sum of element 'Cash' and element 'Petty Cash' must equal element 'Total Cash'). This diagnostic appears because somewhere in the document, one of these calculation rules do not hold. |
Clicking Correct will bring up the XBRL Instance Previewer in Calculation mode, which displays the calculation linkbase in hierarchical form. Elements that fail the calculation validation appear in red. If the user proceeds without correction, the values are exported despite the calculation error. |
|
Abstract tag has been used. |
An object in the document has been tagged with an abstract tag, which are not meant to be used for tagging (typically, they appear in the Presentation linkbase as a means of categorizing other items). |
Clicking Correct will bring up the XBRL Tagging dialog with the tagged object selected to allow the user to remove the tag. If the user proceeds without correction, the tag is not exported. |
|
Global tag is monetary however a non-monetary context ('<context name>') is used. |
A global tag is using a monetary element but has been assigned the specified non-monetary numeric context. This is syntactically correct, but may not be semantically correct. Note that this message may also appear as an error (see Errors table). |
Clicking Correct will bring up the XBRL Global Settings to allow the user to change the context assigned to the global tag. If the user proceeds without correction, the tag is exported despite the context mismatch. Note that this diagnostic only appears when exporting an XBRL v2.0 instance document. |
|
Tagged information is monetary however a non-monetary context ('<context name>') is used. |
An object in the document has been tagged with a monetary element but has been assigned the specified non-monetary numeric context. This is syntactically correct, but may not be semantically correct. Note that this message may also appear as an error (see Errors table). |
Clicking Correct will bring up the XBRL Contexts to allow the user to change the context assigned to the tag. If the user proceeds without correction, the tag is exported despite the context mismatch. Note that this diagnostic only appears when exporting an XBRL v2.0 instance document. |
|
Invalid file reference for a base64 tag. |
An object in the document has been tagged with a base64 tag. This object’s value should be the full path to a file that is to be encoded in base64 format, however the file cannot be found. |
Clicking Correct will bring up the XBRL Tagging dialog with the tagged object selected to allow the user to remove the tag. If the user proceeds without correction, the tag is not exported. |
|
Tagged information is non-numeric however a unit of measure has been assigned to it. |
An object in the document has been tagged with a non-numeric element but has been assigned a numeric unit. |
Clicking Correct will bring up the XBRL Tagging dialog with the tagged object selected to allow the user to change the tag or remove the numeric unit assignment. If the user proceeds without correction, the tag is exported with the numeric unit stripped out. |
| Different values found in items using tag '<tag name>'. | Multiple objects in the document have been tagged with an element in the taxonomy. This taxonomy element has been configured to export a single value only if all tagged values are equal. At least one of these values are different from the rest. If resolved, a single tag will be exported with the resolved value. If no corrections are made, all instances of the tag are exported regardless of the differing value(s). | Clicking Correct will bring up the Goto Tag Dialog. This will enable the user to choose one of the items with multiple tagging and jump to it with the XBRL Tagging dialog open. |
|
Invalid segment defined in Context '<context name>'. |
The specified context in the XBRL Global Settings defines one or more segment elements but at least one of them does not have an element name. |
Clicking Correct will bring up the XBRL Contexts to allow the user to correct the segment information. If the user proceeds without correction, any segment tag with no element name is not exported. |
|
Invalid scenario defined in Context '<context name>'. |
The specified context in the XBRL Global Settings defines one or more custom scenario elements but at least one of them does not have an element name. |
Clicking Correct will bring up the XBRL Contexts to allow the user to correct the custom scenario information. If the user proceeds without correction, any scenario tag with no element name is not exported. |
| Failed to load an embedded subdocument. | CaseView could not load a subdocument that should be included for export (the full path of the subdocument is in the Details area). Any XBRL-tagged data or text content that is in that subdocument will not be included for export. |
Clicking Correct will close the export and jump to the spot in the parent document where the embedded subdocument is located so the user can verify its settings. If the parent document is not yet open, CaseView will open it. |
| A circular subdocument reference has been found. | A circular subdocument reference occurs when a document inserts itself as a subdocument or when a parent document has a series of subdocuments which inserts the parent document as a subdocument (e.g., Document A inserts Document B as a subdocument, which inserts Document A as a subdocument). This would cause infinite repetition of information, so the export will ignore the circular reference. |
Clicking Correct will close the export and jump to the spot in the parent document where the embedded subdocument causing the circular reference is located. If the parent document is not yet open, CaseView will open it. |
| The namespace prefix "<Namespace Prefix>" has been assigned to multiple namespaces. | The namespace prefix <Namespace Prefix> has been assigned to more than one namespace, which would result in an invalid XBRL document. | The XBRL Export will automatically generate a new namespace prefix to avoid the conflict. |
| Unrecognized language code | A tagged item or a footnote has been assigned an unrecognized language code. This indicates the selected code is not in the built-in list of recognized language codes. This diagnostic may also appear if CaseView was not able to load the list containing these language codes. | Clicking Correct will bring up the XBRL Tagging dialog or the XBRL Footnotes dialog (depending on the source of the unrecognized code) to allow the user to select a different language code. If the user proceeds without correction, the language code is exported as is. |
| Unknown Root Node Language Code | An unrecognized language code has been assigned to the XBRL Instance document's root node. This indicates the selected code is not in the built-in list of recognized language codes. This diagnostic may also appear if CaseView was not able to load the list containing these language codes. | Clicking Correct will bring up the XBRL Options dialog to allow the user to select a different language code. If the user proceeds without correction, the language code is exported as is. |
| The footnote with label "<label>" and language "<language>" was referenced but no longer exists. | An object in the document is referencing a footnote that no longer exists. | At the moment, the Correct button is disabled for this diagnostic. This may be enhanced in a future version. If the user proceeds without correction, the footnote, and any references to it by XBRL tags, will not be included in the export. |
| The footnote with label "<label>" was referenced but no longer exists. | An object in the document is referencing a footnote that no longer exists. | At the moment, the Correct button is disabled for this diagnostic. This may be enhanced in a future version. If the user proceeds without correction, the footnote, and any references to it by XBRL tags, will not be included in the export. |
These diagnostics inform the user of an action the XBRL Export has taken. It does not indicate any errors, but the information is provided in case something was done that the user did not intend.
| Information | Description | Notes |
|---|---|---|
|
“<context name 1>” is a duplicate Context of “<context name 2>”. |
The context with name <context name 1> in the XBRL Global Settings contains the same information that would be written to the XBRL Instance Document as the context with name <context name 2>. |
Clicking Correct will bring up the XBRL Contexts to allow the user to change or remove the duplicate context. If the user proceeds without any changes, <context name 1> is not exported and all items that referenced that context will instead reference <context name 2>. |
| “<unit name 1>” is a duplicate Numeric Unit of “<unit name 2>”. | The numeric unit with name <unit name 1> in the XBRL Global Settings contains the same information that would be written to the XBRL Instance Document as the numeric unit with name <unit name 2>. | Clicking Correct will bring up the XBRL Numeric Options to allow the user to change or remove the duplicate numeric unit. If the user proceeds without any changes, <unit name 1> is not exported and all items that referenced that unit will instead reference <unit name 2>. |
| Merged Context “<context name>”. | The context with the given name contains the same information that would be written to the XBRL Instance Document as another context located in another document that is also being exported (the Details area contains the name of this other context and document). | Clicking Correct will bring up the XBRL Contexts to allow the user to change or remove the duplicate context. If the user proceeds without any changes, <context name> is not exported and all items that referenced that context will instead reference the context from the other document. |
| Merged Numeric Unit “<unit name>”. | The numeric unit with the given name contains the same information that would be written to the XBRL Instance Document as another numeric unit located in another document that is also being exported (the Details area contains the name of this other numeric unit and document). | Clicking Correct will bring up the XBRL Numeric Options to allow the user to change or remove the duplicate numeric unit. If the user proceeds without any changes, <unit name> is not exported and all items that referenced that unit will instead reference unit from the other document. |
| Detected use of CV.VER export settings entries | A number of XBRL-related CV.VER settings were deprecated in Working Papers 2017.00 since the corresponding functionality was moved into a new area in CaseView accessible via Tools | XBRL | Options. This diagnostic is meant to inform the user so that they can migrate these settings to the new XBRL Options area. | The user does not need to take any immediate action, but it is recommended to migrate the CV.VER settings to the XBRL Options area. |
Visit us: www.caseware.com | Follow us: 
© 2019 CaseWare International Inc. | Privacy | Terms of Use | Trademarks