gestione parametro in family table a 2 livelli

[summer3d]

hello to all, I have a problem with managing parameters at the second level: I'll explain.

I have a solid "a" that has a family table composed of children "b1", "b2" , "b3"

one or more of their children have other children: So let us take for example the son "b1" who in turn has children "c1" , "c2" , "c3"

in the model father I created a "code" parameter that however will have to be different for each sub-son.
I noticed, however, that I can only manage it until the first-level son.

Is there any shaving to manage that code even at the second level or is it a limit of the program?



Oh, sorry, I have a big family.

help

 

[DANI-3D]

Bye-bye.

I press that multilevel fts try to avoid them as much as possible, because they are of difficult preparation and maintenance, at the beginning they seem a great method, but then I always regret it and I marched back.
in any case ... to be able to exploit it you can assign a code parameter, different for each level and then manage it through relationships, in this way you can enter levels without limits.
I'll give you an example, see if it's your case.

 

[summer3d]

Hello, dany, thank you for the answer.

I too when I can avoid multi-level family like the plague but in this specific case I couldn't.

yes the solution is not what I hoped but I expected that you could not maintain a single parameter for all children so I will find a filling.

Thank you very much to the next one.

 

[calacc]

I think it's enough that you delete the column with the parameter code b1-2-...3; to insert it into the last branch of your family table, then c1-2...3

 

[summer3d]

hi, I also tried as you say, but removing the column "code" from the father's family table to insert it into that of the last child (the second generation I mean ) then it does not allow me to manage the code for the father himself and for the children immediately below (the ones of first generation)

so or I manage the code for the father and the first generation children or only that of the second generation children.

I think it's enough that you delete the column with the parameter code b1-2-...3; to insert it into the last branch of your family table, then c1-2...3

 

[calacc]

the function described is correct. but at qs do first according to me to create a different parameter for a, b, and c and insert the corresponding column in the family-table a, b and c.

es:
father a; code_a parameter (which if it is a unique father you can even avoid doing the ft column);
b1,2,3...n; column with code_b parameter;
c1,2,3...n; column with code_c parameter