Why breakdowns are not created in Indicators?

[Rakshanda Kunte]

Hi All,

Greetings..!!

I am using few Indicators for creating some Data Visualizations in 'Platform Analytics Workspace'. 

Breakdown Requirement:

• Assignment Group
• Incident Type
• Incident Category
• etc. (according to requirement)

Would you please help me with below questions?

1. How many Breakdowns we can add in an indicator or how many are preferred?

2. Does adding multiple Breakdowns as mentioned above affects the performance of Indicator / Jobs?

3. Are there any other issues if we add multiple Breakdowns as per requirement?

Thank you.

[konijetisumanth · Accepted solution]

1) there is'nt any limit specified by ServiceNow, you can add multiple breakdowns,

2) there would not be any effect on indicator but on job please check the system properties set by your platform team for limit set for collecting of data, job take more time to collect but by default only 50000 records can only be stored, but if the limit can be increased by the client.

3)breakdowns feature created to show multiple data analysis in one indicator report so it will not have any issues, but if more then 5 breakdowns are added then the report takes more time to load, but it will not have any issues.

[konijetisumanth · Accepted solution]

once check if any jobs are running for tables u specified then you can utilize them by tagging them to ur indicators, but if its not present you can create jobs 

[konijetisumanth · Accepted solution]

with new features we got to override the default numbers so check below link

Performance Analytics job throws error "Fetched too many rows from indicator source TEST for 2021060...

please click helpfuls bottom if this is helps you.

[konijetisumanth · Accepted solution]

Description and short discretion in entire servicenow is used for any additional or for team management details are given, so  creating a report on them is not a good idea, becoz today it might have something and the next minute it  is not guaranteed to have the same.

but still if you want to have a report , check where the short/description is configured then use that table to create report.

few attributes like discovery sources, first discovered, etc. cannot be created with the table where they are configured rather with sys_choice table.

[konijetisumanth · Accepted solution]

with new features we got to override the default numbers so check below link

Performance Analytics job throws error "Fetched too many rows from indicator source TEST for 2021060...

please click helpfuls bottom if this is helps you.

[Rakshanda Kunte]

@konijetisumanth 

Thanks for all the inputs you have provided on this topic.

Looking for more inputs. 

Que: Is it good or preferred to add Description / short description Fields as a breakdown?

As there is no breakdown or breakdown source currently available.

The requester is creating a trend based on description / short description. 

[konijetisumanth · Accepted solution]

Description and short discretion in entire servicenow is used for any additional or for team management details are given, so  creating a report on them is not a good idea, becoz today it might have something and the next minute it  is not guaranteed to have the same.

but still if you want to have a report , check where the short/description is configured then use that table to create report.

few attributes like discovery sources, first discovered, etc. cannot be created with the table where they are configured rather with sys_choice table.

[Rakshanda Kunte]

@konijetisumanth 

Requirement is to create the new Indicator for Catalog Task/Incident Task/Ctask Tables (as these are not existing)

Here, Can we create one new Job and Indicator/Indicator source for Task Table? Is it a good idea?

and add the breakdown for 'Task Type'. This way it will cover all task types.

This is how I am thinking to implement the request.

Or should we go for separate jobs and indicators as per tables?

Any inputs from your end? 

Thank you..!!

[konijetisumanth · Accepted solution]

As task table is mother of all tables then create a schedule job for Task table and, create multiple breakdowns and add them to indicters and widgets. this should help your requirement.

please click helpful bottom if this is helps you.