You could make one table called Divisions
and another table called Subcontractors
. Each record in the Divisions
would represent one of the divisions, and the Subcontractors
table would include a Link to Another Record field pointing to Divisions
. That way you could link multiple subcontractors
to the “roofing” division. If you turn on record grouping in the Subcontractors
table you’ll be able to group subcontractors by their division.
You could make one table called Divisions
and another table called Subcontractors
. Each record in the Divisions
would represent one of the divisions, and the Subcontractors
table would include a Link to Another Record field pointing to Divisions
. That way you could link multiple subcontractors
to the “roofing” division. If you turn on record grouping in the Subcontractors
table you’ll be able to group subcontractors by their division.
Awesome, great idea! thanks
You could make one table called Divisions
and another table called Subcontractors
. Each record in the Divisions
would represent one of the divisions, and the Subcontractors
table would include a Link to Another Record field pointing to Divisions
. That way you could link multiple subcontractors
to the “roofing” division. If you turn on record grouping in the Subcontractors
table you’ll be able to group subcontractors by their division.
Have one more question: Is there a way to auto-populate a field when a condition is met? Example, division 050000 is Metals and I don’t want to have to worry about writing in the division name after 050000, so can I have the column next to the Division Number auto-populate the name associated with it?
Have one more question: Is there a way to auto-populate a field when a condition is met? Example, division 050000 is Metals and I don’t want to have to worry about writing in the division name after 050000, so can I have the column next to the Division Number auto-populate the name associated with it?
I’m assuming your primary field in the oDivisions]
table is {Division Number}
, and that you have a {Division Name}
field in that same table.
If you want to have {Division Name}
show up automatically in the oSubcontractors]
table based on the {Division Number}
it has been linked to, add a Lookup field to oSubcontractors]
pointing at {Division Name}
.
I’m assuming your primary field in the eDivisions]
table is {Division Number}
, and that you have a {Division Name}
field in that same table.
If you want to have {Division Name}
show up automatically in the eSubcontractors]
table based on the {Division Number}
it has been linked to, add a Lookup field to eSubcontractors]
pointing at {Division Name}
.
Gotcha, thank you. And one last question, certain subcontractors work in multiple divisions and we’d like to have them show up in those divisions when using the grouping view. How do we do that? Would that be something to do with the tags feature?
Grouping will won’t put the same subcontractor in multiple division groups, it will put the subcontractor in a single combined group (“Division 1, Division 5, Division 9”). You could use filtered views as an alternative.
I’d say its worth a shot testing Multiselect Fields as opposed to linking. You’ll run into the same issue with grouping records, but filtering views would be a little easier.