I am looking for some help on creating a Summary Report.
We have Engineers that detail drawings and release the drawings to our shop for fabrication. We track this by the square footage of material on each drawing. In QuickBase our Engineers record how many square feet they release to the shop by entering the square footage amount into a numeric field and the release date into a corresponding date field. They can have up to 16 different releases for each job and the jobs often span over several months. In addition, each Engineer has multiple jobs going on at once.
We want to run a Summary Report that will tell us how many square feet each Engineer has released during each month for the past 12-months.
I have attached a screenshot of my fields.
What I would do instead would be to create a "history" table; where each time they change the SF, you create a duplicate record capturing the value of the SF for that record at that point in time.
This essentially means "duplicating" some of your data into a separate table; from which you can then generate summary reports looking for calculations on SF based on a date range, which in this case would be the [Date Created] or ToDate([Date Created]) value.
This would require your users when entering SF amounts to press a customized button which will save the value and create the historical record in the background returning them to the same page they are on. It would take some training to ensure that they use the right save button; but it would provide you with essentially a history of the changes and allow you to determine for a date range how many SF were changed/entered.
Just make a report where [date 1] is not blank with [Record ID#] the [Date 1] and the [SF 1] as your columns.
Use More .. to Copy these records to another table and map the [Record ID#] into [Related Job] and the other two fields.
That will take 30 seconds.
Edit the report to filter on [date 2] <> blank and change the date and SF columns and do it again,
repeat until all 16 buckets are done.
Then your report will have complete data and you can hide those old fields on the Job record