Issue with multiple level master details

Question

Hi All,
I just came around with following scenario and found it is not working as expected.
GFVO ( Primary Key Attribute -> GFID )
| ---- ViewLink between GFVO and ParentVO on attribute GFID
Parent VO (PrimaryKey PID )
| -- ViewLink between Parent VO and Child VO on attribute ATTR1
ChildVO (PrimaryKey CID )
Data ->
GF VO has record -
1 , xyz
2 , abc
Parent VO
PID Name PGFID ATTR1
1 ppp 1 1
2 ttt 1 2
3 lll 2 1
4 kkk 2 2
Child VO
CID Name ATTR1
1 cc1 1
2 cc2 1
3 cc3 2
4 cc4 2
Requirement is I want to show the name attribute of Parent in Child VO. I have used parent accessor exposed in child to display the name of the parent. When I use this multiple hierarchy in AM and run it I find the wierd result.
Say I select Row (2 , abc) in GF VO.
I should see below two rows in Parent Row.
PID Name PGFID ATTR1
3 lll 2 1
4 kkk 2 2
Now I select Row ( 3 lll 2 1 ) in Parent VO , it shows the following Child ROw I get this result -
CID Name ATTR1 ParentName( accessed throug ViewAccessor)
1 cc1 1 ppp
2 cc2 1 ppp
Gotcha ..... Parent Name ? I am assuming that when we try to access the parent through accessor it will give the parent row from the already filtered VO based on first Viewlink. Rather it requires and gives the first parent as if I m having a single join.
Thanks,
Rajdeep

Answer 1

Hi,
for a master-detail between tables you create a tree binding each. Assuming the data model you defined contains the three view objects in a hierarchy, you simple drag the parent, then the first child and then the second child as a table to teh view. You then configure the PartialTriggers property of child2 table to point to child1 and parent table. The child 1 table partial triggers property will point to the parent table. This should make the m/d work. If on the server you want to use accessors in the code to get to the details of a child (on the client I would use the iterator binding in the PageDef file), make sure you access the correct instance of the ViewOject
Frank