- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-06-2018 09:08 AM
We have been using performance analytics for almost a year. One important breakdown we use is based on the assignment group parent. Everything has been fine up until yesterday when we had to create a couple new parent groups and move groups around from old parents to new parents. Now the assignment group parent breakdown doesn't show all the parent groups, it puts everything in "unassigned". The only other change was adding additional conditions to breakdown and indicator sources just to filter out 2 parent groups we don't want.
Here's what I've tried:
I reverted to the original conditions on breakdowns sources, but that didn't help. I don't really have the option of moving the groups back to their original parent groups. I've checked mapping to be sure nothing has changed and things look fine. It's now been one day, so all jobs ran with the new indicator source and breakdown source condition and it looks like only the parent group breakdown is broken.
Any ideas on what went wrong or help to fix would be greatly appreciated!
Solved! Go to Solution.
- Labels:
-
Performance Analytics
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-06-2018 06:08 PM
Ok... now compare that to your indicator source. What's happening here is your Indicator's more permissive than your breakdown.
Where the indicator has values that the breakdown doesn't, that's when the renderer uses the "Labels for Unmatched".
I'm not 100% what your use case is, but you need to ask yourself if this is a breakdown problem or an indicator problem.
Make sense?
To Illustrate:
- My "New Incidents" indicator just checks for tickets created today. That would be for all groups.
- I then apply my "North American Groups" Breakdown, who's source only has Groups who's locations are NAMR. My Breakdown Source has "Labels for Unmatched" as "those other guys"
- My indicator is naturally pulling NAMR, EMEA, APAC regions.
- My breakdown is only selecting the NAMR groups
- Therefore the EMEA & APAC groups show up as "those other guys"
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-06-2018 12:58 PM
That sounds like the Indicator is drawing more values than the breakdown allows. Meaning indicator pulls A, B, C, D, on a field you use with Breakdown, but the breakdown source is only picking B,C. What conditions did you add to the breakdown?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-06-2018 05:14 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-06-2018 06:08 PM
Ok... now compare that to your indicator source. What's happening here is your Indicator's more permissive than your breakdown.
Where the indicator has values that the breakdown doesn't, that's when the renderer uses the "Labels for Unmatched".
I'm not 100% what your use case is, but you need to ask yourself if this is a breakdown problem or an indicator problem.
Make sense?
To Illustrate:
- My "New Incidents" indicator just checks for tickets created today. That would be for all groups.
- I then apply my "North American Groups" Breakdown, who's source only has Groups who's locations are NAMR. My Breakdown Source has "Labels for Unmatched" as "those other guys"
- My indicator is naturally pulling NAMR, EMEA, APAC regions.
- My breakdown is only selecting the NAMR groups
- Therefore the EMEA & APAC groups show up as "those other guys"
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-06-2018 08:03 PM
Thank you so much! This seems to have me on the right path. I had the same filters on the indicator sources as the breakdown sources, but maybe the fact that some historic data will be unmatched is causing the issue? I'm still not sure how that's failing, but I tried removing the breakdown source conditions again and noticed that old dashboards were back to normal while new dashboards needed to have their jobs ran again for the update to be effective.
My use case is, I have multiple parent groups representing different tiers of support, but I now have 2 new parent groups with child groups that shouldn't be included in any existing reporting. The child groups were pulled from the original 4 parent groups so they could be excluded from reports. I don't want them to show in any indicators on any dashboards we currently use. It looks like data from those 2 new groups is showing up in "unassigned" on various indicators now. How can I eliminate that data from being collected completely?