|
Klasyczne typy plików nie są już dostępne od stycznia 2021 r. Możesz przenieść swoje klasyczne pliki lub pobrać plik PDF. Dowiedz się więcej

XBRL Validation Error - Concept is a Child of itself

Udzielono odpowiedzi
Zamów wersję demonstracyjną

Hi All,

We just encountered an XBRL validation error that we haven't seen before: "Concept is a child of itself." Wondering if anyone has seen this one and know how to resolve. The error description says "A concept in the outline is a child of itself. Right-click the child concept in the XBRL outline and select Remove."

Despite what the error text would imply, it doesn't point to any such situation where a concept has the same concept as a child of itself. The error points to a few spots on the XBRL outline where it seems to have issue with us having two tables in the same abstract that are both using an identical axis concept. 

To be more specific, the error highlights 4 spots on the XBRL outline: Table 1, Axis under Table 1, Table 2, and Axis under Table 2.

We've tried multiple options to clear this, including deleting one of the axes or grouping the tables into separate abstracts, but that hasn't solved the problem.

Anyone have any thoughts or advice on this?

 

1

Komentarze

Komentarze: 2

Data Głosy
  • Madison Ames

    Hi Alexander Haller

    Thank you for reaching out. Follow up question for you, are you using the same axis/domain more than once in the same outline section? If yes, the same members must be nested under both. For example if table one contains the "Property Plant and Equipment [Axis]" with the "Land [Member]" and "Buildings [Member]" nested,  table two will also need to nest both of those members for the second instance of the "Property Plant and Equipment [Axis]". If you do not want the members nested under both you will need to create two different detail outline sections.

    Hope this helps! Happy Tagging!

    0
  • Alexander Haller

    Hi Madison,

     

    That was one the solutions that I tried, but doing so didn't clear the error and it created additional ones that I could only clear by deleting the members that I added.

    We since found a solution, which was to create additional detail sections to that Financial Note and move the tables to separate detail sections. It just seemed odd, because we have other financial note sections that do this same thing and it does not cause an error.

    0

Zaloguj się, aby dodać komentarz.