A control labelled Team or Job Type changes how records are grouped; a control labelled Team A or Team B chooses values within one grouping. Those actions are easy to confuse when a report uses similar-looking slicers. Field parameters can let the reader change the analytical question itself.

Prepare a local Power BI Desktop model with three fictional jobs: A/Install/2 hours, A/Repair/3 hours and B/Repair/5 hours. By team, the hours are A=5 and B=5. By job type, they are Install=2 and Repair=8. Keep those two expected breakdowns available.

Put the parameter in the intended field well

Choose Modeling, New parameter, Fields. Name a dimension parameter and include Team and Job Type. Use a column-based parameter in the visual's axis well and a slicer showing its field names. For a metric parameter, select explicit measures and put it in the values well. Implicit aggregations are not supported as parameter measures; live connections need a local model before parameters can be created.

Start with an existing verified Total Hours measure. Select Team in the dimension control and compare the two five-hour groups. Then select Job Type and expect the two-hour and eight-hour groups. The total workload remains ten, while the grouping and labels change.

If you also offer a verified Job Count measure, test it separately. Team A has two jobs and Team B one; Install has one and Repair two. A switch from hours to jobs must remain clear through the measure name and units, not just a changing bar height.

Exercise more than the first selection

Microsoft documents that supported visuals can display multiple selected measures side by side. Selecting no fields in the parameter slicer is treated like selecting all, not a special empty-field choice. Check those states before deciding whether the control needs a deliberately constrained presentation.

Inspect each available combination against the small job list. Two different groupings happen to give the same overall total here, so a total-only check would miss an incorrect dimension binding. Likewise, a metric switch is incomplete if the chart still labels counts as hours.

Keep ordinary value filters visibly distinct from controls that choose fields. In the final report, give each control a purpose-oriented heading and inspect the initial saved state. Acceptance means the reader can tell what is being measured, how it is grouped and which records are selected, without inferring all three from the position of a bar.

Sources: Microsoft: field parameters.