Measure Names and Measures Values Are Not Retained in Filter

Published: 08 May 2013
Last Modified Date: 18 Oct 2019


After deselecting a measure name from the Measure Names filter, some measure names have disappeard and cannot be added to view again. 

For example, your data contains a Sales measure, if you add it the view and change its default aggregation, it will be now considered as a new measure since its aggregation is different than the original Sales measure in the Data pane. Such a new measure will appear as a new Measure Names, howver if you filter it out of the view, it will no longer exits because the original data source does not contain the same aggregation, therefore it disappears from the filter. 


Tableau Desktop


The measure name must exist in the Data pane. To create such a new measure, please use one of the following options:

Option 1

  1. In the Data pane, right-click on the measures and select Duplicate.
  2. Right-click on the duplicate of the measure and select Default Properties > Aggregation... > Average (change the value as desired)

Option 2

  1. If your new measure is a table calculation, press CTRL + drag the table calculation from the view to the Measures pane.  
    • This will automatically create a calculated field. 
  2. Name the new calculated field. 
    • It will now availabe as a Measure Name. 


Measure Names and Measure Values are unique fields in Tableau. As they are not really singular measures or dimensions (they are considered as a collection of measures that are automatically created based on the measures that are in the data source or created within Tableau). 

When a measure is placed on the measure values card and then it's aggregation is changed (i.e. from a sum to an average) this will be included in the Measure Names quick filter. However, when it is unselected from the quick filter, it is essentially being removed from the Measure Values card because it was originally a sum (not an average), Tableau does not know that it should be added back to the card. 
Did this article resolve the issue?