Help Needed: Understanding PA Tables & Drilldown Setup (Department → Category/Priority)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-13-2025 05:59 AM
Hi Community,
I’m currently working on a Performance Analytics (PA) dashboard and need some help with both the functional behavior and underlying table structure of PA — especially related to drilldowns and breakdown records.
Use Case:
I want to build a widget that:
First displays data grouped by Caller Department.
When I click on a specific Department, it should drill down into details — ideally by Category, Priority, or another breakdown.
What I’ve Done So Far:
Created indicators and added breakdowns (Department, Category, Priority).
Attempted to set up Breakdown Relationships.
Tried configuring a scorecard widget for drilldown, but the breakdowns are not showing as expected during drilldown.
Questions:
How do PA tables like pa_scores_l1 and pa_scores_l2 work internally?
What’s stored in these tables?
How do they relate to the breakdown source and indicator source?
How are breakdown values and scores linked behind the scenes?
For example, how is a department-specific score connected to its Category breakdown?
How does the system determine which records to show during drilldown?
How to correctly configure drilldowns with multiple breakdowns?
Do I need to explicitly set Breakdown Combinations?
Are there any version-specific steps to ensure drilldown options appear?
Are there any best practices or tools (like Analytics Hub) that help verify if breakdown records are being generated correctly?
Any documentation references, real-world examples, or troubleshooting tips would be greatly appreciated.
Thanks in advance for your help!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-14-2025 08:16 AM
Great questions, Balaji — working with PA tables like pa_scores_l1 and l2 can definitely be tricky at first. From my experience, understanding how the system maps breakdowns to actual scores is key. Yes, setting up Breakdown Combinations helps a lot when you're aiming for multi-level drilldowns like Department → Category → Priority. You might also want to check if your data collectors are generating the expected breakdown records behind the scenes.
Also, this is a bit off-topic, but after long PA sessions, I usually wind down with something casual or light-hearted like exploring different game mods — recently stumbled upon https://thesummertimesagaapk.com/ which has a ton of APK-related content. Funny how digging into dashboard logic and debugging sometimes feels like playing through dialogue trees 😄
Hope this helps, and good luck with the widget setup!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-23-2025 09:16 PM
Hi Khanalihaid,
Thanks again for the help — I really appreciate your time and the detailed explanation!
I'm still new to Performance Analytics, and I'm not fully sure how to check whether the pa_scores_l2 table is getting updated — or how to properly verify if the breakdown combinations are working behind the scenes.
Could you please guide me on:
How can I confirm if breakdown combinations are generating scores correctly?
Where to check if the L2 scores are being stored and how to troubleshoot if they’re missing?
Any best practices to debug the data collection process, or any logs/techniques I can use?
Even a small pointer or example would be a huge help as I learn.
Thanks again for supporting me while I get up to speed!