> For the complete documentation index, see [llms.txt](https://knowledgebase.fabricdata.com/fabric-knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.fabricdata.com/fabric-knowledge-base/learn-the-application/destinations/reporting/hierarchy.md).
# Hierarchy
In Fabric, records are linked together through relationships known as Linkages.
* Episodes are linked to a Season.
* Seasons are linked to a Show.
* A Show may be linked to multiple Seasons, as well as to other types of records.
* A Franchise Collection represents a curated collection of various record types.
To support convenient exploration of these relationships, we introduced two reports for navigating the hierarchical structure of records.
This functionality is referred to as Record Hierarchy, and currently has 2 versions
\
1\. Hierarchy V1 (basic)
2.Hierarchy V2 (advance hierarchy)\
Record Hierarchy V1
Version 1 (V1) provides the simplest way to explore the hierarchy of your records.
The linkage relationships are defined as (from highest to lowest)
* Franchise Collection
* Show
* Season
* Episode\*
* Feature\*
* Special\*
* Version
* Version of Version
\
\*Base record is either a
* Feature
* Episode
* Special
Please note that this hierarchy reflects the metadata structure adopted by the majority of our clients. We recognize that requirements may vary, ranging from straightforward implementations to more complex configurations.
Should your metadata follow a different hierarchical structure, please do not hesitate to contact our business team. We will be pleased to review your requirements and configure the hierarchy accordingly to ensure it aligns with your needs.
At each level, you can apply filters on basic metadata + record builder field.
For example, filtering by a Franchise Collection meta Id + imdb id will retrieve all linkages associated with that collection.
#### Record Hierarchy V2
Version 2 (V2) provides a more advanced and flexible way to explore record hierarchies.
\
In V2, the hierarchy is defined from highest (00) to lowest (06) level. Numeric levels are used for clarity, but conceptually they can be understood using family-tree terminology:
* 00 – Great-Grandparent
* 01 – Grandparent
* 02 – Parent
* 03 – Base Record
* 04 – Child
* 05 – Grandchild
* 06 – Great-Grandchild
Using these family-tree concepts, the hierarchy can be visualized as a tree structure.
The term Base Record refers to the central reference point of the hierarchy. It represents the baseline level from which parent and child relationships are evaluated.
As long as linkage rules permit it, you may define and create your own hierarchy reports.
Examples include:
* Shows with Versions
* Parent: Show
* Base Record: Version
* Franchise Collections with Features
* Parent: Franchise Collection
* Base Record: Feature
* Features with Specials
* Parent: Feature
* Base Record: Special
The best way to use this explorer is to:
* Identify your use case
* Apply filters to limit the records at each hierarchy level by category
Example
\
Use case: Retrieve a parent Season and all Episodes associated with it.
\
Apply the following filters:
* Parent Category = *Season*
* Base Record Category = *Episode*
You may further narrow the results by applying additional filters, such as meta ID, title, or other available metadata fields.
#### Custom dashboards/looks
Using the hierarchy explorers, you may also create new dashboards or looks to better suit your specific requirements.
#### Record Builder integration
Each hierarchy has ids, custom fields, synopses and titles based on record builder.
#### Limitation
Please note that the current limitation allows the selection of approximately 61 fields only. This constraint is due to MariaDB’s maximum join limitation, rather than an issue with the reporting tool itself.
There is ongoing DevOps work to migrate all clients and environments to AWS Aurora, which will address and resolve this limitation.
Additionally, any new fields added via the Record Builder are synchronized on an hourly basis. As such, please do not be concerned if newly added fields do not immediately appear in the hierarchy.
