Filtering Summary Reports
Hello! I have a table with the following fields:
Name (text)
Check-in Period (date)
Pulse (Numeric)
I would like to have a report that shows ONLY employees whose average pulse over t...
Forum Discussion
MarkShnier__You
Qrew Legend
Qrew LegendI suggest a different approach.
Make a summary field on the relationship between employees and pulse measurements and summarize the Average Pulse Rate for the last three months. The make a standard table report of Employees with filter of
[Average Pulse Rate Last three months] is less than or equal to 3.
------------------------------
Mark Shnier (YQC)
[email protected]
------------------------------
Make a summary field on the relationship between employees and pulse measurements and summarize the Average Pulse Rate for the last three months. The make a standard table report of Employees with filter of
[Average Pulse Rate Last three months] is less than or equal to 3.
------------------------------
Mark Shnier (YQC)
[email protected]
------------------------------
Awesome solve Mark! A little more context for Addie:
The issue you’re running into stems from filters applying before the summarization happens, which means filtering out individual Pulse records changes the final averages. That’s why simply filtering for Pulse ≤ 3 removes rows you still need for the calculation.
Some Extra Fun:
Sometimes we use this create summary fields and then push them back down to the child table as a look-up field. This could be used to create rankings, or used to grab things like "latest child record" by using record ID. There are tons of cool use cases using this strategy.