Explanation/Reference:
Explanation:
Book hierarchies that have large numbers of levels, with records at every level, behave in a similar way to the team functionality where manager visibility is enabled. Such hierarchies perform well with small data sets. However, as data volumes grow, books with fewer levels in the hierarchy (or with no hierarchy levels) perform far better than team functionality.
If one level of your book hierarchy provides no additional value to data security or data organization, merge the redundant book and its subbooks. Ask book users if they can typically identify whether a record is in one subbook or another subbook of the same parent book; if they cannot, it indicates that the best option is to collapse the two subbooks into the parent book.
A simple method of reducing the number of levels in a book hierarchy is to prefix subbooks with the name of the parent book. For example, if you have a subbook called North with a parent book called North America, remove the parent book, and rename the subbook as NA - North.
NOTE: Books at the lowest level of a hierarchy are called leaf-node books.