Breakdown relations not showing label for unmatched correctly

[jasonhagen]

Has anyone else experienced an issue with the breakdown relations not showing the label for unmatched defined in the breakdown source?   I have an issue where the breakdown and relations are functioning correctly, the hierarchy defined works flawlessly.   However, the unmatched records do not show up when the widget breakdown is navigated via the breakdown relation defined.   I don't see anywhere in the breakdown relation record to force to define a new unmatched label.   Any help would be greatly appreciated.   I am on Istanbul release.

[pieter_goris]

Hi Jason,

for me this sounds like the right behavior, but maybe i'm missing a use case in my reasoning. When scores are collected for a breakdown (let's assume for assignment group), the 'unmatched' is used whenever there is an unknown group (element) or no group.

With breakdown relations you navigate from a first level breakdown element to another first level breakdown element, based on a relation between the two elements. So one could navigate from the "parent" assignment group to the "children" assignment groups; or from an assignment group to its "sibling" assignment groups (groups that share the same "parent").

Navigating from/to an unknown or empty group will not work as it does not have relations with other groups.

Hope this helps.

Cheers, Pieter

[jasonhagen]

Pieter,

Thank you for the reply.   The logic of your response is sound; however the data relationships lend themselves to a potential bug in the breakdown relations.   The data that is expected to be unmatched are children to the parent first level - does that make sense?   Here is an example, the first level breakdown is IT Service; each IT Service has 1 or no child Service Offerings.   Since Service Offering is optional at present time, it is often times left empty (null) hence the need to display the unmatched, but the null is still against the first level of IT Service.      

Expected output:

IT Service (first level breakdown):   Mobility 8

Service Offering (child to first level):   Cellular 4

                                                                                                                      (unmatched) Unknown 4

I hope this makes sense.

Best Regards,

Jason

[Arnoud Kooi]

Hi Jason,

As mentioned by Pieter you are hopping to another 1th   level breakdown when using a breakdown relation.

There is a score for the unmatched service offering, but this is the total of empty service offerings.

Check the simple sample below where the total unmatched is 5, not 4.

So to check the number of empty Service Offerings for the Mobility IT Product, we need to drill down to the second level of scores.

If you have enabled Collect Breakdown Matrix on your Indicator, you   should be able to do so.

[Khadijah Vinson]

Hi,

I have the same question.  The above really pointed me in the right direction however, i did update my indicator and checked the collect breakdown matrix as mentioned above.  However on the widget, are you supposed to add addition elements where it states"unmatched"?  If I where to click on the search function next to element where it says "unmatched" it only provides me a list of all my elements with the same sub-category, but different value, it is using the same table.

Not sure how you can create another parent/child if this is a sub-category with alot of values that are being unmatched.

Thanks,

Khadiajh