INVOICE_GRID_ANALYTE_HDR_FIELD

STRING, comprising an analyte attribute in the format:

attributeName

or

tableNameAlias.attributeName

When Maintaining Job Invoice Samples and Tests from Registration or Maintaining the Samples and Tests on a Job Invoice in an Invoice to maintain the invoice sample grid on a job invoice, then the content of analyte column headers is set based upon this preference. When a column that contains an analyte is displayed in the CCINV—Invoice application, then:

  • If empty (default on deploy), then the value of the default attribute is used as the column heading (see below).
  • If not empty, then the system attempts to find the value of the supplied attribute.

The table name aliases are JSA for job scheme analyte, SA for scheme version analyte, and U for unit.

The analyte attributes are defined by the related DTO property name (displayed when the cursor hovers over a screen field where the Show attribute tooltips setting is enabled).

Where analyte attributes are taken from SA or U, then they are taken from or via the org-scope (not the enabled-scope), or the lab-scope.

The column heading is set using the following rules:

  1. Where either:
    1. The preference is not defined
    2. The preference's value is inactive
    3. The preference's value is empty
    4. The preference's value does not contain a recognisable attribute name within JSA, SA or U
    5. The preference's value contain a table name alias but does not contain a recognisable attribute name within that table

    then the scheme version analyte's Name is used as a default. For example:

    • <empty> --> S.name
    • xxx --> SVA.name
    • XXX.xxx --> SVA.name
    • JSA.xxx --> S.name
    • JSA.name --> SVA.name
  2. Where either:
    1. The preference's value does not contain a table name alias, but contains an attribute name within JSA, SA or U
    2. The preference's value contains a table name alias that does not match JSA, SA or U, but contains an 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 --> SVA.name
    • reportName --> JSA.reportName
    • priceCode --> JSA.priceCode; SVA.code when price code empty
    • exportName --> SVA.exportName
    • XXX.name --> SVA.name
    • XXX.reportName --> JSA.reportName
    • XXX.exportName --> SVA.exportName
  3. Where the preference's value contains a table name alias matching JSA, SA or U, and contains an attribute name within that table, then it is used. For example:
    • JSA.reportName --> JSA.reportName
    • JSA.priceCode --> JSA.priceCode; SVA.code when price code empty
    • SA.name --> SVA.name
    • SA.reportName --> SVA.reportName
    • SA.priceCode --> SVA.priceCode
    • SA.exportName --> SVA.exportName
    • unitCode --> SVA.name (Unit codes are not supported)
    • U.unitCode --> SVA.name (Unit codes are not supported)
    • U.name --> SVA.unitCode >> U.name

The supported analyte-based attributes are:

Job Scheme Analyte

Scheme Version Analyte

Unit

activatedUserId

alignment

code

compositeQcStatus

allowNullResult

convertToUnitSuffix

compositeSpecStatus

allowReportNonValData

creationDate

creationDate

analyteTextId

creationTime

creationTime

analyteType

creationUser

creationUser

applyCorrectionFactor

description

id

autoAvgReadings

id

isReportable

autoRelease

isActive

jobCode

autoValidate

lastModDate

jobSchemeId

creationDate

lastModTime

laboratoryCode

creationTime

lastModUser

lastActivatedDate

creationUser

longSymbol

lastModDate

datagridHeaderName

name

lastModTime

defaultDataEntryWidth

unitCategoryId

lastModUser

defaultToFirstListValue

 

organisationCode

description

 

registrationSequence

displayMask

 

reportDescription

exportName

 

reportName

falseValue

 

reportSequence

holdingTime

 

requiredDate

id

 

schemeCode

includeOnWorksheet

 

schemeLaboratoryCode

isAccredited

 

schemeVersionAnalyteId

isIncludeInCosts

 

workflowStatus

isInvoiceable

 

 

isMandatoryProfile

 

 

isOnlyFromList

 

 

isReportable

 

 

isSavedToQcHistory

 

 

isSurrogateResultCritical

 

 

laboratoryCode

 

 

lastModDate

 

 

lastModTime

 

 

lastModUser

 

 

msdsName

 

 

organisationCode

 

 

parentAnalyteId

 

 

registrationSequence

 

 

repeatability

 

 

repeatRangeTableCode

 

 

reportDescription

 

 

reportName

 

 

reportSequence

 

 

reportUnitId

 

 

reprodRangeTableCode

 

 

reproducibility

 

 

roundingMethodType

 

 

schemeCode

 

 

schemeVersionId

 

 

spreadsheetFormula

 

 

surrogateRecLowerLimit

 

 

surrogateRecUpperLimit

 

 

surrogateTargetValue

 

 

uncertaintyType

 

 

unitId

 

 

upperAnalyteCode

 

 

upperSchemeCode

 

 

warningTime

 

It is suggested that the maximum length should be 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