# 7.9 Get list of all template paths in a project (global or otherwise)

**URL:** <https://forum.inductiveautomation.com/t/7-9-get-list-of-all-template-paths-in-a-project-global-or-otherwise/36233>\
**Category:** Ignition\
**Tags:** ignition79\
**Created:** [July 1, 2020, 6:48am UTC](https://forum.inductiveautomation.com/t/7-9-get-list-of-all-template-paths-in-a-project-global-or-otherwise/36233 "2020-07-01T06:48:06Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![nminchin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nminchin/32/6911_2.png) [@nminchin](https://forum.inductiveautomation.com/u/nminchin)\
**Post date:** [July 1, 2020, 6:48am UTC](https://forum.inductiveautomation.com/t/7-9-get-list-of-all-template-paths-in-a-project-global-or-otherwise/36233/1 "2020-07-01T06:48:06Z")

</div>

I’m trying to produce a list of all templates in a project (including the global project), which there isn’t a python function for, so I’ve found the resources within the config.idb:

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/4/5/455278cc78a8ba40457d5f2fff86e998f3d24056.png)  
However, their full path doesn’t seem to be stored in the same table, I only see the resource name.  
Where would I find a list of the parent paths?

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [July 1, 2020, 2:41pm UTC](https://forum.inductiveautomation.com/t/7-9-get-list-of-all-template-paths-in-a-project-global-or-otherwise/36233/2 "2020-07-01T14:41:30Z")

</div>

If I remember the old project resources system correctly, the `PARENTUUID` is a reference to the containing folder, which will either be a special singleton root folder (as in your screenshot) or some other resource (type `__folder`). The UUID of that folder resource will be encoded in the `data` property of the folder. It’ll be a 16-byte binary representation of the UUID. You’ll have to (recursively) walk that sequence of folders up to get the full path to nested resources.

If it doesn’t go without saying: Doing what you’re doing isn’t supported. 🙂