Forum Discussion
QuickBaseCoachD
8 years agoQrew 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.
- JimHarrison8 years agoQrew ChampionAhhhhhh!!! Thanks, I couldn't find this little nugget.
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.
- QuickBaseCoachD8 years agoQrew CaptainQuick Base is not difficult. Except that there are like hundreds of easy things to learn. So you need to stumble hundreds of times once. Now you know this trick and hopefully you just need to stumble once per nugget learned. Or else watch all the videos in the Quick Base University. https://university.quickbase.com/
- JimHarrison8 years agoQrew ChampionHow do you deal with records getting deleted out of order? I have three records with snapshot 1,2,3. I delete record 2 and create a new record. Now I have records, 1,3,3. If I set this to be unique I get an error.
Is there a solution? - QuickBaseCoachD8 years agoQrew CaptainWell one choice is to not allow records to be deleted, but rather just marked as inactive.
The other option is to do another "loop" and do a summary maximum of the maximum snapshot value, and then look up that field down to the child records and then do a final snapshot field. Then that will not change if a record is deleted. - NicolasBizouard5 years agoQrew MemberWoaho! 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
------------------------------