@Chris Davidson needs a break ;-) but we're definitely going to do something a long the lines of learn / test your knowledge while you play. @Meghan Johel might help us, so we make sure to keep that real world Premier CSM perspective in the game :-) 

Are we resetting the challenges for 2019?

Thanks @Myda Balingcongan!!!

@Usha Shrestha

Thanks. Didnt knew Challenge 2 was out

You've still got time!  Due tomorrow!!  Challenge 2: Detect most recent server location and status [+] 

@Phaneendra Sristi, food for thought...

did I miss the next challenge by any chance :O

I confirmed with Chris. Challenge two coming next week! (April 2-6) :-)

He is - hopefully I can get this one ;-)

Me, too, Christy - I'm not as well-versed in reporting personally - more of a model chick - even with my limited knowledge lol - but on the bright side, we receive the correct answer later and learn something new! 

Next month! @Chris Davidson are you cooking one up? 

This looks fun! I'm sad I missed the first question -- when's the next one

Woohoo thank you Rhonda

Whew that took me a minute, but your badges and points are awarded. @Steven Young, @Julie Batty, @Melissa Cunningham; @Chrystie Lambert, @Daniel Swainston, @Craig Solomon, @Jonathan Strauss, @Suresh Sawlani Steven Cornish you've all earned one game piece and 30 points. 

@Chris Davidson will post the next chance to win in April. 

@Julie Batty, @Melissa Cunningham @Chrystie Lambert @Daniel Swainston @Craig Solomon @Steven Young @Jonathan Strauss @Suresh Sawlani Steven Cornish  #nailedit

Congratulations all!!!  And keeping this one for future reference!!  

Congratulations to 9 of you who submitted a correct answer:

Steven Young
Julie Batty
Melissa L. Cunningham
Christina Lambert Pastella
Daniel Swainston
Craig Solomon
Jonathan Strauss
Suresh Sawlani
Steven Cornish

Locking a report component (table, chart, KPI, etc.) fully to 3 objects triggers a relatively large drill calculation, so this functionality is intentionally limited to partial drills when a third model object is involved.

I cannot drag Cost Source.Cost Pool into the Rows area of the ad hoc query configuration area, but I can drag Cost Source.Cost Pool into the Filters area instead, and then edit the filter to include only Cost Pool=Internal Labor values. My report table won't mention internal labor (since Cost Pool is not a visible table column), so I should probably label the table as "Labor-related server cost per app" or something similar. I can view the table data path to confirm it drills between 3 objects:

Applications/
.DrillTo/
IT Resource Towers/
.DrillTo/
Cost Source/
!FILTER[{Cost Source Master Data.Cost Pool}="Internal Labor"]/

Another option: add a slicer to the report, and drag Cost Source.Cost Pool into the slicer's Slice By area. This is nice because (1) it allows users the option of locking to the third object, and (2) it visually emphasizes the presence of the third object lock, instead of me having to add an explanatory label to the table.

Keep in mind that Staging and Production environments do not precalculate all possible combinations of slicer selections, so be aware that you may be causing report users to experience wait times when they interact with the slicer - and these wait times will be higher than usual because we're locking to three model objects instead of just to one or two objects.