A [Shipping Priority] dimension holds the members Low, Medium, High and Critical. Whenever the analyst drags this field onto Rows in any new worksheet, the members appear alphabetically as Critical, High, Low, Medium, but the team always wants them to read Low, Medium, High, Critical without re-sorting each sheet. Which action makes that order the field's standing behaviour across new views?
- AApply a manual sort on the axis in one worksheet, which carries that order to every other worksheet using the field.
- BSet a Default Sort on the field as a default property, defining the manual order Low, Medium, High, Critical so it applies wherever the field is used. Correct
- CConvert the field from a dimension to a measure so the members order themselves by value rather than alphabetically.
- DCreate aliases on the members so their display names begin with numbers that force the desired sequence.
Why A is wrong: A sort applied on an axis is local to that worksheet and does not propagate to other sheets that use the same field.
Why B is correct: Correct: a default sort stored in the field's Default Properties imposes the chosen member order across every view that uses the field.
Why C is wrong: Turning the field into a measure would aggregate it and remove the discrete members entirely, so there would be no Low to Critical headers to order.
Why D is wrong: Aliases change only the displayed text; renaming members would not impose a custom order and would also change how the categories read.