What is causing my Indicator from not collecting breakdown data?

[ChristineP]

Use case:  Provide a list of service desk users and their % of KB articles attached for incidents worked.

I created a Database view called “Knowledge Article Task User [u_knowledge_article_attached_user] to join with the sys_user table so that I can show in the Breakdown the users name id instead of the Created by(which is the user id) and the Database view provided me with the Name ID from the Sys_user table that I want to show in my breakdown.

See attached document that shows screen prints of the indicators and breakdowns created. 

1. In my Indicator source, why can't I select the Database view created when the indicator uses the database view as the fact table?

2. My Breakdown source is using the Database view able, why is the data not showing?

[Adam Stout]

1) When we collect records, we store the sys_ids.  Since views don't have sys_ids, you have to select the "View Table" which is selecting which set of sys_ids you want to collect.  Do you want to store the sys_ids for the KB info (the use) or the user?

2) Breakdown mappings need to be to a choice or a sys_id.  You are mapping to a string so you won't get any results since the breakdown source is a list of sys_ids.  The actual user id won't be found in the list of sys_ids.  The user's sys_id should be though.  I think you'll want to map to usr_sys_id, assuming the breakdown source is on sys_user (probably with a related list condition to ensure it is only KB attachers) or perhaps to sys_user_grmember for members of the service desk.  I would not create a breakdown source on a fact table as this may cause performance problems.  Any breakdown source not on the sys_id field is concerning to me.  There are valid use cases, but I prefer hitting the base table with a related list condition if needed.

[ChristineP]

I am looking to get the User who Attached the KB Article name and how many they created.