Platform

Β View Only

 Compact Slicer not working on all group tables

Jump to  Best Answer
  • TBMStudio
Apptio Community Member's profile image
Apptio Community Member posted Wed April 27, 2022 01:43 PM
Hey everyone! I've got a group of tables on a report in TBM studio and I'm trying to use a Compact Slicer to filter all tables in the group by the Project Number. The TEST table in my screenshot works with the slicer when the Project Number is the only thing in the table. Once I add anything else, the slicer no longer filters the entire table.

It does appear to be filtering the cost values in the table, so anything besides the selected project will have a cost of $0. But it won't actually filter the table down to just the one project's line item. 

The Slicer is based on a Project Dataset and the grouped tables are based on that same Dataset and a Transform of it, in case this information helps. 

Does anyone know what I'm missing or doing wrong here? 

TEST table isn't being fully filtered by compact slicer.

#TBMStudio
Ben Foster's profile image
Ben Foster posted Mon May 02, 2022 08:16 AM  Best Answer
Hi Jessica!

I would filter out zero records by going clicking the table > click the "Data" tab > click the "Zeroes" button in the Data Ribbon > and click the check boxes for your metric you are using to filter out those zeroes.

-Ben
#TBMStudio
Jenny Franklin's profile image
Jenny Franklin posted Wed April 27, 2022 01:52 PM

Hi Jessica - have you tried encapsulating all tables within a group?


#TBMStudio
Guillermo Cuadrado's profile image
Guillermo Cuadrado posted Thu April 28, 2022 03:49 AM
@Jenny Franklin's idea of using Groups looks perfect for your use case, @Jessica Matos.

I haven't used Groups, but we have Tabs in many reports, and it works the same way: any slicer outside the tab object works on all reports inside each tab.
#TBMStudio
Justin Hazelrigg's profile image
Justin Hazelrigg posted Thu April 28, 2022 07:39 AM
Hi Jessica, a couple solutions come to mind depending on your situation.
Are the fields from the same model object? Project ID should be Project ID whether its in your Cost Source or Project object, but depending on how your model is set up they could be coming from different sources so make sure the slicer and table are using the same d.
Next would be to change the compact slicer to a global from local, it can be overkill and doesn't really address why the connection of the table and slicer is not working can solve the issue, but may create another problem for users if the report is part of a report collection it will filter the other reports on that value as well.
#TBMStudio
Apptio Community Member's profile image
Apptio Community Member posted Thu April 28, 2022 08:51 AM
@Jenny Franklin all 3 tables are already in a group :( thank you for the suggestion though!

@Justin Hazelrigg I believe it's the same Project ID, since the only other table being used is a transform of the table with the original project ID. Also the TEST table and the one directly beneath it are based on the exact same data. I will try the global filter though! Thank you!​​
#TBMStudio
Jenny Franklin's profile image
Jenny Franklin posted Thu April 28, 2022 09:11 AM
Morning!  If you're unable to find a solution, definitely reach out to your CSM! 😊🀩
#TBMStudio
Guillermo Cuadrado's profile image
Guillermo Cuadrado posted Fri April 29, 2022 02:11 AM

Hello, @Jessica Matos. On second thought, this might be because you are using two different objects in your report group. You write the slicer has the Project ID from the Projects object. If you are using a different backing table for the other tables in the report, this might be the issue. For us humans it is evident it's all the same thing. The engine seems to think differently.

1) I tried having two tables (Original & Transform) without any model relationship. When I tried to slice by the master's Project ID, Apptio issued the usual error that there is no relationship between both tables:



2) I then added a relationship as follows:

I used a data relationship based on Project ID. This may not be your setup, but anyway.

This is what I got, regardless of whether I had the slicer inside or outside the group:


I still think it's because the column in the slicer is not the same as the one in the transform table. Also, I realize your setup might be different from the one I tested, but do contact me or expand on this post, please.


#TBMStudio
Jenny Franklin's profile image
Jenny Franklin posted Fri April 29, 2022 08:57 AM
Apptio Community Member updated Fri April 29, 2022 08:58 AM

Guillermo is making me remember something that happened to me the other day.  I was doing a report with slicers from two different objects and it worked one time, and then it didn't.  I had to rebuild the whole thing.  Have zero idea if this is what it was, but I built everything first and pulled in the Cost metric very last.  Have you tried using perspectives, too?
#TBMStudio
Apptio Community Member's profile image
Apptio Community Member posted Sun May 01, 2022 08:11 AM
@Guillermo Cuadrado I do have a model relationship between the two tables, but the fact that they are different tables could still be part of the issue. I appreciate you looking into this! I'm going to try a combination of tweaking the allocation/data relationships between the two and @Jenny Franklin's suggestion of using perspectives. I hadn't thought of that, but using a modeled metric seems to be throwing it off, so the perspective might address that piece.

Thank you both so much!​​
#TBMStudio
Jenny Franklin's profile image
Jenny Franklin posted Mon May 02, 2022 08:28 AM
Excellent suggestion, @Ben Foster!  Should've thought of that seeing as that exact situation bit me a few months back ugh! πŸ€¦β€β™€οΈβ€‹
#TBMStudio

Related Content