Platform

Platform

A place for Apptio product users to learn, connect, share and grow together.

 View Only
Expand all | Collapse all

First report slicer influence content second slicer

  • 1.  First report slicer influence content second slicer

    Posted Tue July 02, 2019 08:29 AM

    We all know that report slicers in the same report influence other slicers when 'By state' has been set.

     

    In the situation that you select a value in the first slicer that generates actually one value in the second slicer only (one on one relation), the value in the second slicer will be bold reported at the top of the list. See the following screenshot as an example where Global HR is selected in the first slicer and Cost Center 5010007 is bold reported at the top of the list in the second slicer.

     

    For a one on one relation between two slicers and values we prefer that the value in the second slicer (in this case Cost Center 5010007) is directly shown in the Compact Slicer Cost Center like the following screenshot.

     

    Does anybody know a solution for this?





    #Platform


  • 2.  Re: First report slicer influence content second slicer

    Posted Tue July 02, 2019 09:53 AM

    I played around with it and the only thing I can think of is making cost center a "Row Slicer" and make it wide enough so you can see the top remaining result highlighted.


    #Platform


  • 3.  Re: First report slicer influence content second slicer

    Posted Tue July 02, 2019 03:19 PM

    @Menno Wittebol,

     

    To further @Jason Tucker's suggestion, you can add a column to the master data and concatenate these 2 fields so the users can now either search by name or cost center in one slicer -- this is a workaround. I don't think I can think of a direct solution as you requested. 


    #Platform


  • 4.  Re: First report slicer influence content second slicer

    Posted Wed July 03, 2019 02:08 AM

    Hi @Tony Wong, you idea is actually also nice idea we use in other circumstances but in this situation it generates a very wide column which is not preferred.


    #Platform


  • 5.  Re: First report slicer influence content second slicer

    Posted Wed July 03, 2019 02:04 AM

    Hi @Jason Tucker, Your idea is actually a nice solution however the Row Slicer has the annoying side effect that you have to scroll through the selection list instead of a pulldown list you have with the Compact Slicer.


    #Platform


  • 6.  Re: First report slicer influence content second slicer

    Posted Wed July 03, 2019 09:38 AM

    Yes, I noticed the scrolling issue and I figured that would be a show stopper. I don't play around with HTML enough, but I wonder if there is an HTML box you can display that will show the cost center when the department is selected. That may be too complex.


    #Platform


  • 7.  Re: First report slicer influence content second slicer

    Posted Tue July 02, 2019 01:40 PM

    @Menno Wittebol, is there always a one for one relationship between the content of the parent slicer and child slicer?


    #Platform


  • 8.  Re: First report slicer influence content second slicer

    Posted Wed July 03, 2019 01:55 AM

    Hi @Shannon Lynch, unfortunately there are not always one on one relations between Department and Cost Centers. A Department can have multiple Cost Centers.


    #Platform


  • 9.  Re: First report slicer influence content second slicer

    Posted Wed July 03, 2019 02:53 AM

    For now and as a work around, we added a Column Picker to add additional columns to the report to show the Department and Cost Center values immediately in the report when required.

     


    #Platform


  • 10.  Re: First report slicer influence content second slicer

    Posted Wed July 03, 2019 08:44 AM

    That's a good workaround, @Menno Wittebol.


    #Platform