Breakdown Relation - Relating Category to Subcategory comes up with either no results or erroneous results

[Jason D2]

Good morning,

I'm having a hard time getting a breakdown relation up and running. I've got a breakdown for Incident Category and a breakdown for Incident Subcategory. When time I go to an indicator's scorecard, I breakdown by Category, and then try to breakdown by the Breakdown Relation I've made.

PROBLEM
Depending on how I've setup my Breakdown Relation, I'll either get no result.

Or I'll get a result that seems to include the appropriate subcategories, but I'm assuming also includes every single duplicate from other categories with an identical name. So if 6 categories have an "other" subcategory, it seems like it's aggregating all of the "other" subcategory values into one:

SETUP
Each source is working off the sys_choice facts table, via the sys_id field. They filter by incident table, element (category or subcategory respectively), and language (en).

My Breakdown Relation attempt is below. I've tried almost every configuration of the limited fields the sys_choice table gives me, but this is almost the only one coming back with any results. If I do the same thing, but change the Related breakdown field to sys_id, then I strangely get zero results. Am I running into issues because the "Dependent Value" field is a string (i.e. Hardware, System Generated, etc...) taken from the Category label, and not a reference to the sys_id of the category?

I'm getting stumped. Any tips, help or ideas you guys can provide would be much appreciated!

EDIT: In further messing around, I've realized that setting a Common Field of Dependent Value trims out the duplicate Subcategories (yay!) but it also seems to get rid of any count from subcategories with duplicates (boo!). In actuality, the 'Other' subcategory should be showing a count of 22. Not 0, and not 119.

[Jason D2]

So, I've realized something about these "duplicate" subcategories. I believe somewhere along the way, my PA configuration is saddling a single Category with every record with subcategory "Other", while the remaining categories get zero. I'm not sure where I need to make this segmentation happen, but I'm wondering if it's going to need to involve scripting?

[ManosijSengupta]

Hey Jason

Can you share the solution , if any for the above question

[Jason D2]

Hi monty3110, I'm sorry to say I never did fully figure this out, just had to move on to other things. If you stumble upon anything, please let me know!

[Jason Monzo]

Hi Jason D,

Breakdown relations are a way to "side hop" from one breakdown to another.  Following a breakdown relation will not always result in a drill-down on the first breakdown.  For instance, I could be looking at an element of an assignment group breakdown and follow a breakdown relation that includes all of the group members.  The sum of the group members could be more than the score of the group, and that is OK because some members may be in other groups as well.  I didn't drill into the originally selected group.  Rather, I hopped from the assignment group breakdown to the assigned-to breakdown and filtered the element list to only include people in the original group.

A drill-down, on the other hand, is the process of subdividing a data set into smaller and smaller chunks.  For instance, I have 10 incidents in the performance category.  There are three subcategories for performance.  I would like to see those same 10 incidents broken down by subcategory.  I expect to see three values or less that add up to 10.

So, that leads me to the question of whether you want to hop from category to subcategory or drill-down from category to subcategory.

If you want to drill-down, then you only need to make sure both breakdowns are related to the appropriate indicators and the "collect matrix" box is checked.  If necessary, recollect your data, and you're all set.

If you want to hop, then you need to properly define a breakdown relation.  In order to do that, you need a table with at least two columns--one referencing elements of the first breakdown by unique ID (usually sys_id) and one doing the same for the second breakdown.  This table may or may not already exist in your instance.  I'm pretty sure that it does not exist in your case.  This is what you specify in the "Table" field, and the two columns go in "Breakdown field" and "Related breakdown field".  The "Common field" field is for sibling-type relationships.  For instance, I may want a relationship that includes all of the other assignment groups with the same parent as the selected group.  The documentation linked below explains all of this in detail.

https://docs.servicenow.com/bundle/london-performance-analytics-and-reporting/page/use/performance-a...

Regards,

Jason Monzo