Forum Discussion
MarkShnier__You
Qrew Legend
4 years agoBen,
I think that you are saying that you have Relationships where One Project has Many Pallets and One Pallet has many Pieces.
Why not just make a combined text summary field to summarize the unique pieces up to Pallets and then summarize that field again up to Projects?
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
mark.shnier@gmail.com
------------------------------
I think that you are saying that you have Relationships where One Project has Many Pallets and One Pallet has many Pieces.
Why not just make a combined text summary field to summarize the unique pieces up to Pallets and then summarize that field again up to Projects?
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
mark.shnier@gmail.com
------------------------------
BenKrieger
4 years agoQrew Member
The relationship structure of my app is Projects have many work tickets, which have many travelers, which have many pieces. Projects also have many pallets which have many pieces. I was summarizing all of the pieces that passed final QC and weren't already on a pallet up through travelers, work tickets, and finally to projects to get a list of all the pieces that were final approved and not palletized for each project and then passing that list as a lookup to the pallets table so that each pallet record could use that list for data validation. I need a way to get that Quality Control information from the Piece records to the pallet records so that users will not be able to associate a piece that is not final approved by QC with a pallet.
A combined text field was my initial solution, however combined text fields are treated as multi-select fields which have a maximum of 20 outputs. The problem with this is that the number of pieces that are final approved by Quality Control and not palletized could easily be over 20 pieces for any given project at any given time. Using a combined text field would mean that for any project where this is true the combined text field would return an incomplete list.
------------------------------
Ben Krieger
------------------------------
A combined text field was my initial solution, however combined text fields are treated as multi-select fields which have a maximum of 20 outputs. The problem with this is that the number of pieces that are final approved by Quality Control and not palletized could easily be over 20 pieces for any given project at any given time. Using a combined text field would mean that for any project where this is true the combined text field would return an incomplete list.
------------------------------
Ben Krieger
------------------------------
- MarkShnier__You4 years ago
Qrew Legend
Combined text summary fields will return the first 150 unique children. So much more than 20.
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
mark.shnier@gmail.com
------------------------------- MarkShnier__You4 years ago
Qrew Legend
Here is some help on various Quickbase limits
https://help.quickbase.com/user-assistance/quickbase_limits.html
"The maximum number of text values that a combined text summary field can accumulate is 150."
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
mark.shnier@gmail.com
------------------------------- BenKrieger4 years agoQrew MemberIt seems you are correct, I was mistaking that only 20 selections can be made from a Multi-Select text field, not that only 20 can be returned. In that case I believe 150 would be enough. Thank you for your help.
------------------------------
Ben Krieger
------------------------------