hey bart thanks - that worked!
I suppose I was more trying to capture the children as well under the assets - incase images etc was updated hence why I was trying to use the tree location. But for basic content it should assist the team.
so if we needed larger areas but wanted to capture specify nodes we would set two triggers?
- One for the parent ( incase it is changed the tree ID)
- then another for the children - using the tree location and defining the parent as the node?