Hierarchy load and Section Access

[amien]

i have a master table which contains a NodeID and ParrentID (Employees).

with the HIERARCHY load i build up my Hierarchy-Tree with employees. All works fine, but not i want to add Section Access on this tree.

So when a certein employee logs in, he should only see this own tree (up and down)

BUT he shouldn't see any facts on the upper nodes in the tree.

I don't know where to put on what field i should put the Section Application on. Or do i need to loop though all the node fields to reduce the data?

Anyone got a good example?

Thanks in advanced

[hic]

I would use the HierarchyBelongsTo prefix to create a bridge table between the user's root node and all sub nodes. It really doesn't matter if this bridge table is in Section Access or in Section Application. Either way will work.

Hence, three tables:

1) Authorization table (in Section Access) with USER/NTNAME and ROOTNODE

2) Bridge table (loaded with HierarchyBelongsTo) with ROOTNODE and Node

3) Transaction/Data table (in Section Application) with Node and other data

HIC

[amien]

Thanks for your reply!

This works like a charm, but i still have one issue.

It happens that a certain employee falls under two different parents. When i do the above, the 'other' parent Hierachy will also show. So i will have another tree besides the tree of the person that is logged in. All the employees that are in the other tree, are also in the tree that i want. I just don't want to see that tree.

Do you have a solution for that?

[avinashelite]

Hi Amien Amien / Henric Cronström

Can you please post the sample code or app for implementing section access with  Hierarchy-Tree with employees.