Breakdown mapping script not setting values properly

SBratcher
Tera Expert

I am trying to create a dashboard widget that will show how many RITMs were submitted with each of the options specified in one of two variables.

 

I used the details from this older post to create my script, https://www.servicenow.com/community/platform-analytics-forum/how-to-create-breakdowns-on-catalog-va...

 

SBratcher_0-1670944627027.png

the gs.info output shows appropriate RITM numbers and topics and the scorecard for the indicator lists all of the available options, so the script is definitely getting the right data, but the indicator scores are all showing up in the catch-all "other" breakdown item rather than the appropriate topic.

 

Does anyone have any idea where I might have gone wrong? The only other scripted mapping I have written used buckets so this is a bit new.

13 REPLIES 13

Ok. And what happens when the indicator is shown on the analytics hub?

Does it show the breakdown on the left? Do you have a screen?

 


If I helped you with your case, please click the Thumb Icon and mark as Correct.


All of the items end up in the other category:

 

SBratcher_0-1670952504484.png

This is a subset of what shows up in the scores:

SBratcher_1-1670952610674.png

 

When I search the logs for those exact three items this is what the script is sending:

SBratcher_2-1670952717127.png

 

Yeah... it is not "breaking down anything".

Try using a PA bucket like this PA script does: /pa_scripts.do?sys_id=b1562cc5d7100200b96d45a3ce6103fd

Breakdown source using the PA bucket: /pa_dimensions.do?sys_id=c496acc5d7100200b96d45a3ce6103e2

 


If I helped you with your case, please click the Thumb Icon and mark as Correct.


I can set it up that way to test, but that is not actually an answer to the problem I am trying to solve.

 

Using a bucket means that we would have to maintain the same information in multiple places since if there was a change to the catalog item's choices I would have to update the bucket group as well as the script to accommodate the change, or else our report would be incomplete. 

I know. I don't like it either but while you are doing that you might find what is the problem.


If I helped you with your case, please click the Thumb Icon and mark as Correct.