We’ve added a new section into our debug pane of a template, called the Dependencies tree. It’s a double-sided tree graph, representing both the forward and backward dependencies of the template you are debugging.
The template you are debugging, is the root of it all, sitting in the middle of the tree.
left -------|
|
|
root
|
|
|------- right
On the left, you’ll see the templates in which our current template depends on (using their results for example).
On the right side, you’ll see the templates in which they depend on the current template.
So think of the tree as a flow of results from left to right.
Here’s an example:
Couple of notes to be added:
- Due to the high number of dependencies in production templates, we reduced the tree depth to only 3 levels (including the root), with the 2nd-level nodes collapsed by default and we’re only taking into account the dependencies from the current period (the template could also be referenced by future or previous periods, for example
period.minus_1y.reconciliations) - Since generating the tree can be expensive for templates with lots of dependencies, it is only initiated after the debug section “Dependencies tree” is expanded for the first time. So you can still use the debug pane without any effect in performance - the tree will be generated on-demand, so only if you need it
Hope this can help you at when building a set of templates that all need to work with one another 
Be sure to check out our original topic about the main functions about the debug pane: