Configuring Report Drilldowns

[tim_treacy]

Why?

[David Hepburn]

Has it always been like this?  or did this behavior start recently?

If memory serves, there was a chromium update recently that negatively impacted scrollbar behavior in some situations.  If this behavior is new-ish, it's possible you're seeing undesired behavior bc of that update. 

I never had any issues in Firefox or Vivaldi, so I didn't keep an eye out for the fix. 

Possibly something to look into 🤷‍

edit:  Drilldowns are so much easier to configure and perform much more smoothly in Platform Analytics.  If you haven't begun exploring there yet, I definitely recommend it 🙂  it's really slick, and classic reporting will be deprecated in a couple of versions if I understand correctly. 

-- David

[tim_treacy]

Not related to the scrollbar behavior.  We determined that was related to the chromium update and the Grammerly browser extension.

And No, this isn't a recent.....been like this for a while.   I just ran into it again, and actually took some time to see if I could find some configuration to control or adjust it (and I couldn't).

(fyi: Any adjustments to the 'Custom chart size' in the parent reports config has no impact on the chart size of the drilldown, and the drilldown config doesn't include the Custom chart size boolean.  The annoyance at this is what got me to finally post about it.)

[tim_treacy]

Forgot to include the screenshots.

In the Custom Size config of the parent report, I can make the pixel dimensions as large as I want.....

Regardless of what size it's made, the dropdown defaults to the 'stock' size.

[tim_treacy]

---

@David Hepburn wrote:

edit:  Drilldowns are so much easier to configure and perform much more smoothly in Platform Analytics.  If you haven't begun exploring there yet, I definitely recommend it 🙂  it's really slick, 

---

Appreciate the suggestion, but the specific need for this report is to identify data discrepancies between tasks, with the chart is showing the 6-mo. volume, broken down by Task Type.  However, there's also a need for direct access to the tasks (hence the drilldown).
The use of reports here is that it offers that combo:   allowing us to display the volume, and providing quick access to the underlying records, without leaving the dashboard it's on.

In PA, those actions aren't quite so straightforward....so while we do use PA,  IMO, Indicators don't really serve the same purpose. 

---

@David Hepburn wrote:

and classic reporting will be deprecated in a couple of versions if I understand correctly. 

---

Man, I hope not.....given the LoE and config overhead of PA, the productivity impact losing the ability to spin up simple reports will be......painful (for my Org).