Before creating a new display column in a report, the analyst should check that no suitable column has already been created. Display columns are reusable records, and an established environment is likely to contain one that retrieves the required data point. Reusing it saves time, keeps the library of columns manageable and ensures that the same data point is presented consistently in different reports. The first option is correct. Always creating a new column for customization would lead to duplication and make maintenance harder. Consulting the Clarity Dictionary is not relevant, since Workbench columns read from Chronicles and the dictionary describes Clarity. Using SlicerDicer to prototype is a different analysis tool and does not establish whether a column exists. The most effective way to search is by the master file and the item number of the data point, since columns with different names may still read the same item. If no suitable column is found, the analyst can create one with a clear name and description. Documenting it helps others to find and reuse it later.
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit