Forum Discussion
NickBellows
3 years agoQrew Member
My concern is scale. My example is a much scaled down version of my actual situation. In reality I have something like 50 positions and will eventually have dozens of cohorts. I don't want to the field to be selectable from a list of Managers to choose. I want it to populate with the name for that position in Table 1.
I am starting to think that because of the conditional nature i.e. Task 2 is assigned to Cohort B and the owner of that task is Manager, I need to create a query to the First Table. Not sure I know how to do that.
------------------------------
Nick Bellows
------------------------------
I am starting to think that because of the conditional nature i.e. Task 2 is assigned to Cohort B and the owner of that task is Manager, I need to create a query to the First Table. Not sure I know how to do that.
------------------------------
Nick Bellows
------------------------------
MarkShnier__You
Qrew Legend
3 years agoI suggest that you make a Child table of Cohort Positions.
One Cohort has many Cohort Positions. Set a Custom Key field to be the hyphenated value of [Related Cohort] and Position.
Make a formula to calculate the key field and then use a form rule to populate the scalar Key field.
Then this Cohort Positions table can be a Parent to Tasks. The field for Related Cohort Position on the child can be calculated.
------------------------------
Mark Shnier (YQC)
mark.shnier@gmail.com
------------------------------
One Cohort has many Cohort Positions. Set a Custom Key field to be the hyphenated value of [Related Cohort] and Position.
Make a formula to calculate the key field and then use a form rule to populate the scalar Key field.
Then this Cohort Positions table can be a Parent to Tasks. The field for Related Cohort Position on the child can be calculated.
------------------------------
Mark Shnier (YQC)
mark.shnier@gmail.com
------------------------------