Field Paramenter Slicer Side Effect

I just discovered a challenging side effect from using a field parameter slicer to define a column value in a matrix visual.  The following parameter slicer enables the user to select a specific value from the date table to define the column definition in the visual:

Period Slicer = {

    ("Day", NAMEOF('Date Table'[Date]), 0),

    ("Month to Date - MoM", NAMEOF('Date Table'[Year Month Name]), 1),

    ("Month to Date - YoY", NAMEOF('Date Table'[Year Month Name 2]), 2),

    ("Full Month - MoM", NAMEOF('Date Table'[Year Month Name]), 3),

    ("Full Month - YoY", NAMEOF('Date Table'[Year Month Name 2]), 4),

    ("Quarter to Date - QoQ", NAMEOF('Date Table'[Year Quarter Name]), 5), 

    ("Quarter to Date - YoY", NAMEOF('Date Table'[Year Quarter Name 2]), 6),

    ("Full Quarter - QoQ", NAMEOF('Date Table'[Year Quarter Name]), 7),

    ("Full Quarter - YoY", NAMEOF('Date Table'[Year Quarter Name 2]), 8),

    ("Year to Date", NAMEOF('Date Table'[Year]), 9),

    ("Full Year", NAMEOF('Date Table'[Year]), 10)

}

The problem is that when the user clicks on a specific column, it does not filter the Date Table. (see the Filtered Date Min and Filtered Date Max card values)

How can I get the Date Table to filter itself by the selected column or collection of selected columns using this field parameter method?