Snapshot a Report in Time

You can have a Pipeline calculate your Summary Data and write that to a dedicated table.

Assume you want to know what your Sales Team is Forecasting to Sell for this month.  Forecasts change everyday if they are talking to the customer. However the forecast on the first day of the month is the bench mark for the month.

The Opportunities table may have dozens of records with a forecast close date for the month,  we calculate that value on the first day of the month and write a single record for each sales rep in the Opp Summary table.  You now have total dollars for the 1st day of every month and can do your analysis on them with no fear of it changing.

As ​@DonLarson has suggested, you would use Pipelines to write this data.  If the data is totals based on each Parent (Table A); then you could write the summary values to static/scalar fields in your Table A - meaning that you generate the summary data once and write it into the Parent Record.

Alternatively if your summary data needs to be aligned differently (anything other than the Table A parent-record id#) then you would write this data (via Pipelines) to a new table.  This would support repeated-data capture as well, if needed.

Can you illuminate whether the summary data is based on the Parent-Relationship or based on something else.

To build on Don's answer, since you want the snapshot tied to the Table A record, I'd make a child table of A (say "Snapshot Lines") and let a pipeline fill it. Trigger on Record Created in Table A, Search Records in Table B with whatever filter defines the analysis, then write the rows into Snapshot Lines with the Table A Record ID# as the related parent. Bulk record sets (Prepare Bulk Record Upsert, Loop, Add a Bulk Upsert Row, Commit Upsert) is the efficient way to do that write. Your summary report then runs off Snapshot Lines filtered to that parent, and it never moves when the sync refreshes B.

https://help.quickbase.com/docs/use-the-quickbase-channel

https://help.quickbase.com/docs/bulk-record-sets

Matthew, Top Step Technology

To build on Don's answer, since you want the snapshot tied to the Table A record, I'd make a child table of A (say "Snapshot Lines") and let a pipeline fill it.

Trigger on Record Created in Table A, Search Records in Table B with whatever filter defines the analysis, then write the rows into Snapshot Lines with the Table A Record ID# as the related parent.

Bulk record sets (Prepare Bulk Record Upsert, Loop, Add a Bulk Upsert Row, Commit Upsert) is the efficient way to do that write. Your summary report then runs off Snapshot Lines filtered to that parent, and it never moves when the sync refreshes B.

(https://help.quickbase.com/docs/use-the-quickbase-channel)
(https://help.quickbase.com/docs/bulk-record-sets)

Or copy the app. 🤔