Hi Michael! You can do this by putting SUM() around all the field names, like this:
IF SUM([Visit Calculated Miles ])>=0 AND SUM([Visit Calculated Miles ])<60 THEN 0
This switches the calc to an aggregation calc instead of a row-level one.
On another note, you could probably simplify this calculation considerably since your buckets just increase by 30. Perhaps you could divide by 30, round down, and then multiply that by 0.5. For instance:
FLOOR(SUM([Visit Calculated Miles ])/30) * 0.5
Thank you for such an expedient response. I should have mentioned in my original post that the Visit Calculated Miles ] measure was already an aggregated calculation which is SUM([Visit Calculated Miles])/COUNTD([Branch Group]). So I couldn't put SUM's in front of that measure as it was already aggregated.
Perhaps some examples of my data will help to demonstrate better. Below you can see what my calculation does when data is viewed at the "daily" level. It works great. However, below that I've included what it looks like if I view by week, then miles get added for the whole week, and not calculated day by day and then summed for the week after that. How can I get results that are calculated at a "daily" level, but then viewed and summed appropriately at the "weekly" level?
Day of Date - Visit And Non-Visit Activity Mileage Bonus Points 19-May-16 1.5 20-May-16 1.5 23-May-16 1 24-May-16 0 25-May-16 1.5 26-May-16 0 27-May-16 0 29-May-16 1.5 30-May-16 1.5 31-May-16 1 1-Jun-16 1.5 2-Jun-16 0 13-Jun-16 0 14-Jun-16
versus when my view changes to (Week Beginning by)
Week of Date - Visit And Non-Visit Activity Mileage Bonus Points 15-May-16 null 22-May-16 5 29-May-16 null 12-Jun-16 null 19-Jun-16 4.5 26-Jun-16 4.5 3-Jul-16 5 10-Jul-16 5
Ah, I see. Can you share a packaged workbook so I can see all the calcs and how the data is laid out?