How to breakdown map a field from an extended table?

[Dario Marquez]

I have an indicator based on the task_time_work table and I need to break it down by "category" which is a field from the incident table. I already have the "category" field breakdown from the incident table. But in the mapping form, when I try to map it to the task_time_work table, I select in the facts table ="task_time_work" and in the field I am able to get to the "task" table but I am not able to get further to the extended table "Incident". How can I do this? Thanks

[Harsh Vardhan]

it can be done through the scripted. 

kindly check the scripted check box and write script to get it. 

adding one example here, give a try. 

How to Create Breakdown Mappings for Child Class Table when Breakdown Fact Table is a Base Table

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

[Adam Stout · Accepted solution]

Either use a script to dot walk to the field which would look something like this (assuming I want incident_state from a task reference:

current.ref_incident.incident_state;

Or you can create a database view to join the data so it is not an extended field.  However, the indicator source has to change which can be an issue if this is already live.

[Dario Marquez]

Hi Adam, thanks for your reply. I tried your script to map the breakdown. But I am still getting this error:

I need to map or connect the "task_time_worked" table to the "task" table and then to the "incident" table. So I tried this script:

The "task" is the field of the first table "task_time_worked" that has the incident number and refers to the task table to the "number" field,  then "number" is the field of the task table that connects to the incident table, and the "u_category_ch" is the field from the incident table that I need as a breakdown. I am using the correct names and not labels of the columns. Not sure if its because I am double dot walking that this is not working and I need to used a different syntax. I am thinking that the problem could be that task has many extended tables like "case" or "incident" and they both have columns with the same name. Could be happening that the name is ambiguous and the script doesn't specify the table therefor cannot find the field? But not sure where to go from here. Help is appreciated. 

[Adam Stout]

Did you select the field in the field list of the script?