To enable end users to analyze SalesAmount by ProductCategory, Year, or CustomerCity using a single column chart with minimal development effort, what modeling feature should you implement?

To enable end users to analyze SalesAmount by ProductCategory, Year, or CustomerCity using a single column chart with minimal development effort, what modeling feature should you implement?

• A. Set up a Fields parameter with ProductCategory, Year, and CustomerCity. Use the Fields parameter in the visual
• B. Create separate visuals for each axis and switch between them
• C. Use a slicer connected to measures for each dimension
• D. Create calculated columns for each category and year

Answer: (A)

Dynamic field selection in a single visual is achieved by using a Field parameter that contains the fields ProductCategory, Year, and CustomerCity. When you bind the visual’s axis to this parameter, end users can switch which field drives the column chart without creating additional visuals or measures. This keeps the report lean and lets users analyze SalesAmount across different dimensions from one chart with minimal development. Why this is the best fit: it provides a single, flexible chart that adapts to the chosen dimension, reducing maintenance and deployment effort. The parameter-based approach also scales cleanly as new fields are added, unlike building separate visuals or numerous calculated columns for every combination of dimension. Why the other options aren’t as suitable: creating separate visuals for each axis would clutter the report and require extra work to keep them synchronized. a slicer connected to measures for each dimension adds complexity and still doesn’t swap the axis of a single chart automatically. creating calculated columns for each category and year bloats the model and isn’t scalable for new data values or dimensions.

Dynamic field selection in a single visual is achieved by using a Field parameter that contains the fields ProductCategory, Year, and CustomerCity. When you bind the visual’s axis to this parameter, end users can switch which field drives the column chart without creating additional visuals or measures. This keeps the report lean and lets users analyze SalesAmount across different dimensions from one chart with minimal development.

Why this is the best fit: it provides a single, flexible chart that adapts to the chosen dimension, reducing maintenance and deployment effort. The parameter-based approach also scales cleanly as new fields are added, unlike building separate visuals or numerous calculated columns for every combination of dimension.

Why the other options aren’t as suitable: creating separate visuals for each axis would clutter the report and require extra work to keep them synchronized. a slicer connected to measures for each dimension adds complexity and still doesn’t swap the axis of a single chart automatically. creating calculated columns for each category and year bloats the model and isn’t scalable for new data values or dimensions.