QEHNick Posted November 14, 2022 Share Posted November 14, 2022 Hello everyone, I must be having a bit of a brain fart as I cannot work out why my measures for Priorities Met/Missed are so wildly different. For example (based on h_dateresolved), Missed priorities (h_withinfix =0) percentage for a particular team last month was 13.43%; looks great, but if I do one for met priorities (h_withinfix=1) I get 41.79%. Where's the other 44 odd percent gone? This is the same for all such measures. What am I missing here? Cheers. Link to comment Share on other sites More sharing options...
Steve Giller Posted November 14, 2022 Share Posted November 14, 2022 @QEHNick Are you restricting the report to statuses of closed/resolved? Do you have any Requests that don't have an SLA attached? I'm sure there are more gotchas here, but they're the ones that spring to mind. Link to comment Share on other sites More sharing options...
QEHNick Posted November 14, 2022 Author Share Posted November 14, 2022 No Steve, I'm using h_datersolved for date ranging, h_pk_reference as value column. Where clause is h_requesttype and h_fk_team_name. Percentage sub-query is h_withinfix=0 Key column is h_pk_reference Usual table. Link to comment Share on other sites More sharing options...
QEHNick Posted November 14, 2022 Author Share Posted November 14, 2022 Oh... Doh! I see where you're coming from now. Should I be doing that? Link to comment Share on other sites More sharing options...
QEHNick Posted November 14, 2022 Author Share Posted November 14, 2022 I thought just having the h_withinfix value being 0 or 1 would suffice for an indicator on it being resolved/closed. Link to comment Share on other sites More sharing options...
SamS Posted November 14, 2022 Share Posted November 14, 2022 Hi @QEHNick, The withinfix field is only valid/populated once the timer is marked (i.e. very likely at resolution/closure in the BP). Prior to closure it's like Schrödinger's cat. Link to comment Share on other sites More sharing options...
Steve Giller Posted November 14, 2022 Share Posted November 14, 2022 16 minutes ago, QEHNick said: I thought just having the h_withinfix value being 0 or 1 would suffice for an indicator on it being resolved/closed. 48 minutes ago, QEHNick said: Where's the other 44 odd percent gone? h_withinfix can also be null, so without picking the report apart (which I'm not very good at anyway) my assumption would be that accounts for the "missing" 44% Link to comment Share on other sites More sharing options...
QEHNick Posted November 14, 2022 Author Share Posted November 14, 2022 Based on the supposition that the resolve status needs to be specified, I have created another measure with those criteria. The results are exactly the same. Link to comment Share on other sites More sharing options...
Steve Giller Posted November 14, 2022 Share Posted November 14, 2022 I would suspect that either there are requests without an SLA, or there's another criteria I'm missing. Probably one for one of our reporting experts here, unless you can specify h_withinfix is not null, maybe? Link to comment Share on other sites More sharing options...
QEHNick Posted November 14, 2022 Author Share Posted November 14, 2022 Wow, adding h_withinfix IS NOT NULL has smacked that figure up significantly. I'll analyse it further to see if that was what was missing. Cheers for your thoughts @Steve Giller Link to comment Share on other sites More sharing options...
QEHNick Posted November 14, 2022 Author Share Posted November 14, 2022 I think that's done it, it now matches up, Missed/Met percentages. A thousand thanks. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now