Field parameter in Table – how to control or rename column headers?

Use the following appraoch.
Step 1: Create a disconnected table for the switcher

Create a table with your period options:

Switcher = DATATABLE("Period", STRING, {{"Daily"},{"Monthly"}})

This table is not related to any other table in your model.

It will act as a slicer for users to select either Daily or Monthly.

Step 2: Create a dynamic measure

Create a measure that returns the correct value based on the selection:

Dynamic Value =
VAR SelectedPeriod = SELECTEDVALUE(Switcher[Period], "Daily")
RETURN
SWITCH(
    SelectedPeriod,
    "Daily", [Daily Measure],
    "Monthly", [Monthly Measure]
)

Replace [Daily Measure] and [Monthly Measure] with your actual measures.
It picks the selected period from the slicer.
The measure will show the correct value in the Table based on the slicer selection.
Step 3: Use the measure in the Table

Add your Dynamic Value measure to the Table visual.
The Table will now only have one column for values, and the column header will be the measure name (e.g., “Dynamic Value”), not the field parameter name.
Step 4: Dynamic Table title

If you want the Table header to reflect the selection:

Table Header Title = "Showing: " & SELECTEDVALUE(Switcher[Period], "Daily")

Place this measure in a Card visual above the Table.
This lets users know whether the Table is showing Daily or Monthly data, without renaming the column itself.

Thank you cengizhanarslan 

This pattern works technically, but it doesn’t fit my model because I already use calculation groups + a field parameter to handle Daily/Monthly globally.

In my case:

• Daily vs Monthly logic is centralized in calc groups, so wrapping measures again with SWITCH() would be redundant and hard to maintain.

• The disconnected switcher pattern only swaps values, it does not switch the grouping column (Date vs Month), which in my model is handled by a field parameter.

• Using this approach would require creating “Dynamic …” versions of many measures (Actual, Budget, Variance, Delta, etc.), which goes against the goal of having one reusable base-measure pattern.

• I already have a single synced slicer driving both the calc group and the field parameter; introducing another disconnected switcher would duplicate that logic and risk desynchronization.

So while the approach is valid for simpler models, it doesn’t work well with a calc-group-driven, field-parameter-based design like mine.

You can’t rename, hide, or dynamically control the column header created by a field parameter in a Table visual. If possible, switch to a Matrix and:

• Put the field parameter in Columns

• Put your dimension fields in Rows