Breakdown on Task type doesn't work as intended

[andersbogsjo]

Hi!
I have breakdown (and Breakdown Source) on Task Type (Source on sys_db_object). 
The names of the tables is from a Scooped Application(which are available from all Application Scopes) and the preview shows exactly thoose tables

Then I have the Automated Breakdown which (as far as I know) is correctly made and mapped correctly.

It is sen connected to an Indicator and when I run the jib I get all the Records but no Breakdown?

There are no Job errors or anything.
What am I missing?
@Adam Stout maybe?
I have similar Breakdowns for other Task Types (incident, problem etc) that is working.
Regards
Anders

[Mohith Devatte]

Hello @andersbogsjo ,

Just checking if all the three tables from scoped app are extending task table ? 

please check that . if its not extending then sys_class_name wont return these three tables  names.

Hope this helps 

Mark the answer correct if this helps you 

Thanks

[andersbogsjo]

There is one table in between that is Extended from task table and the three tables are extented from that table.
/Anders

[Adam Stout · Accepted solution]

The breakdown is on sys_id (which is correct) but the mapping is to a string, not a sys_id. You either need to add a PA script to look up the sys_id for the class from sys_db_object or use a database view to join task to sys_db_object to task to get the sys_id. 

The script will have a significant performance hit because you are now running a query for every row in task.  The database view requires some setup but will performance MUCH better.

[andersbogsjo]

Great!
Thanks Adam for the input!

I will set up a Database View for this!

Regards

Anders