Choose a Power BI Measure When a Result Must Respond to Slicers
A per-job duration and a total for the currently selected team are different kinds of result. Choosing the calculation object deliberately makes an interactive Power BI report easier to understand. Do not assume a stored column should rewrite each job's value when someone selects another team.
Prepare a local imported practice table called Jobs with a job ID, Team and numeric Hours. Give Team A three jobs lasting 1, 2 and 3 hours, and Team B three lasting 4, 5 and 6 hours. The full total is 21; the team totals are 6 and 15.
Match the object to the question
Microsoft distinguishes calculated columns, evaluated row by row during refresh and stored in the model, from measures, evaluated as needed in filter context. Measures can respond to report selections. A calculated column can still be grouped or aggregated in a visual; that does not mean the stored value for each row is recalculated by the selection.
In Power BI Desktop, choose Modeling, New measure and enter Total Hours = SUM(Jobs[Hours]). Add this explicit measure to a card or other value visual. Keep a separate table visual showing the job IDs and their Hours so the summary has an inspectable record basis.
Use a Team slicer to select A. With the intended interaction applied, the measure should return 6 and the visible job rows should be A's three records. Their individual durations remain 1, 2 and 3. Selecting B should give 15 with its 4, 5 and 6 hour records.
Check a changing total without changing a job
Clear the selection and confirm 21. Then inspect one job's original stored value. The different totals describe different included sets; they are not edits to the recorded duration of that job.
If the card does not respond, inspect whether the slicer is filtering it and whether the visual uses the intended measure. In a larger model, also trace the relevant relationships and any filters deliberately removed by the measure. Replacing every column with a measure would not resolve an unrelated filter-path problem.
Keep the metric definition with the report: which numeric field is totalled, what one source row represents and which selections should affect it. Accept the calculation only when both the total and its contributing records agree. This distinguishes a correct interactive summary from a familiar number that happens to match one initial view.
Sources: Microsoft: calculation options; Microsoft: supporting procedure.