Comments
-
Will this work?
-
One question though, will the BeastMode look at <.07 Warning and pick up .05 OR since it is top down, it will stop at .06 line and a .065 would then trigger Warning for .07?
-
As always, thank you for the guidance Mark! Michael
-
@jaeW_at_Onyx @MarkSnodgrass it looks like removing the additional fields, adding back last_sync with MAX aggregation and adding NAME gives me the most recent sync date per machine! Michael
-
@MarkSnodgrass I dragged last_sync and chose MAX aggregation as well as created a BeastMode with MAX('last_sync') and I am still seeing the same output. Michael
-
@jaeW_at_Onyx also, where is the switch to enable filter on aggregates? I believe it would be a useful function for the dashboards we are developing.
-
@jaeW_at_Onyx so I actually have a dataflow in order to bring in last_sync from the inventory report (as well as other fields) since the patch report does not have last_sync field. So your suggestion would be to remove duplicate machines with older sync dates in the dataflow? Michael
-
This is great information in regards to calculating rolling average however, what I am attempting to is create a time period/date function for Microsoft Patch Tuesday's that looks at "last_sync" date field with "Review Period is between Previous Month Second Tuesday to Current Month Second Tuesday = True". One idea I had…
-
Excellent suggestion and I appreciate the exposure to the dataset view!!
