SAMPLE_GRIDDING_ANALYTE_HDR_FIELD

STRING, comprising an analyte table column or DTO attribute name, of String type data, in the format:

recordTypeAlias.TABLE_COLUMN_NAME/attributeName

or

TABLE_COLUMN_NAME/attributeName

This preference sets the field displayed in the analyte column header when Applying Sample Gridding for a job or job scheme.

The recordTypeAlias is the table/DTO name alias: JSA for job scheme analyte, SA for scheme version analyte, and U for unit.

The table column or DTO attribute names (either can be used, as long as they contain string-type data) are case-sensitive. The target field is not found if case is not matched. Therefore, table column names must be upper-cased to work, and DTO attribute names must be as they appear when the cursor hovers over a screen field where the Show attribute tooltips setting is enabled, or in screen personalisation for the DTO service.

Note: Where table column or DTO attribute names are taken from SA or U, then they are taken from the org-scope (not the enabled-scope), or the lab-scope.

The column heading is set using the following rules:

  1. Where any of the following situations exist, then the scheme's Name is used as a default:
    • The preference is not defined
    • The preference's value is inactive
    • The preference's value is empty
    • The preference's value does not contain a recognisable column/attribute name within JSA, SA or U, matching on case, for example: REPORT_description, or XXX.xxx
    • The preference's value contains a valid record type alias but does not contain a recognisable column/attribute name within that table, for example: JSA.xxx, SA.exportName, or JSA.POSSIBLE_DATE
    • The column/attribute does not hold a string-type data
  2. Where the preference's value does not contain a record type alias but contains a column/attribute name within JSA, SA or U, or the preference's value contains a table type alias that does not match JS, SCH or SC but contains a column/attribute name within JSA, SA or U, then the first occurrence of the field within JSA, SA and U, in that order, is used. For example:
    • name --> SA.name
    • reportName --> JSA.reportName
    • priceCode --> JSA.priceCode; SVA.code when price code empty
    • exportName --> SA.exportName
    • XXX.name --> SA.name
    • XXX.reportName --> JSA.reportName
    • XXX.exportName --> SA.exportName
  3. Where the preference's value contains a record type alias matching JSA, SA or U, and contains a column/attribute name within that record type, then it is used. For example:
    • JSA.reportName --> JSA.reportName
    • JSA.priceCode --> JSA.priceCode; SVA.code when JSA.priceCode is empty
    • SA.name --> SA.name
    • SA.reportName --> SA.reportName
    • SA.priceCode --> SA.priceCode
    • SA.exportName --> SA.exportName
    • unitCode --> SA.name (Unit codes are not supported)
    • U.unitCode --> SA.name (Unit codes are not supported)
    • U.name --> SA.unitCode >> U.name

The maximum length should be about 10 characters as a greater length than this causes the headings to consume the entire screen, preventing scrolling and making the grid unusable. Custom attributes are not supported for the sample grid.

Typically the preference is not set at role or user level.

Related Processes