Pretty sure I know the answer here - but I have seen a lot of people do some cool stuff with saved searches so here it goes:
I often run into situations where I need a summary search (like SUM all events of a certain type in a calendar, or transaction, or anything) as an example. Works great.
BUT...
Then I want to do some math on that against another value... maybe from the search or maybe even hardcoded IN the search.
So in the above example lets say on the employee record I have a value 10 for the number of days allowed off in a year for the employee (but any example works - this is a universal challenge regardless of the record type)
If I source THAT FIELD with the value 10 into the search... if there is ONE record in the results for that employee - the SUM function and subsequent math will show "they had 1 day off" and the math is "10 days from employee record" - "1 day from days in calendar"... and my results look great = Employee X has 9 days of vacation left!
BUT... when there TWO result (or more) the summary works like this:
The SUM function says "they had 1 day off" (result 1) and "they had 1 day off" (result 2) then say ok - 2 results, need that value from the employee record two times to match so "10 days from employee record" and "10 days from employee record"- "1 day from days in calendar" +"1 day from days in calendar"... and my results look great = Employee X has ((10+10)-(1+1)) 18 days of vacation left!
Again any example where you want to do math in a summary search against a static value is killer.
Is there any way to do any of the following:
1) pass summary amounts into formula fields in a summary search i.e. COUNT the number of records and then use that COUNT to divide by the static value in the example above - the results there would work correctly
2) any formula function you can wrap a field in that will tell the summary function DON'T act on this. So in the above example you could perhaps do DONT_SUMMARY_FUNCTION(10) - {days_off_in_calendar} - so the 10 would NOT be added per "result" but the days off would- so the math would come out correctly.
3) carry the results from 1 formula field into a variable to be used in another field on the search later?
Anyone ever find a way to manage this challenge: use a summary search to compute a value when one of the variables in the calculation is static regardless of the number of results?