Forum Discussion
QuickBaseCoachD
Qrew Captain
You have not really described you table and their relationships, but the usual trick is to do a summary field of the # records and then look that up back down to the child table. Then create a new field which is a numeric field type and edit its field properties to make it a snapshot of the lookup field. That snapshot will stay frozen once snapshotted and not change when the next child is created.
That field property setting is at the bottom of the field properties page. Note that it will not retroactively fix existing records. That snapshot is frozen when the record is saved.
That field property setting is at the bottom of the field properties page. Note that it will not retroactively fix existing records. That snapshot is frozen when the record is saved.
NicolasBizouard
4 years agoQrew Member
Woaho! it works exactly the way I want it to. Once you select snapshot, it offers to initialize from all records. So don't worry about implementing late in project.
My need was to county Risks and Issues for subcustomers. So you follow up the above, your subcust table is the parent. I've created 2 summaries (Risk - Issues) ; this allows to make a different count for each sub customer. Tomorrow morning I'll be the king of my team :) ; thanks guys!
------------------------------
Nicolas Bizouard
------------------------------
My need was to county Risks and Issues for subcustomers. So you follow up the above, your subcust table is the parent. I've created 2 summaries (Risk - Issues) ; this allows to make a different count for each sub customer. Tomorrow morning I'll be the king of my team :) ; thanks guys!
------------------------------
Nicolas Bizouard
------------------------------