POS Layout Field Object Reference
On this page
Overview
POS Layout Fields belong to a Pos_Layout record and define which Salesforce fields are loaded and rendered in the POS. Each field can optionally point to a Pos_View to render a custom Liquid template in place of the raw field value, and its Type token string controls whether it is visible, indexed in the browser’s IndexedDB, and included in keyword searches.
| Property | Value |
|---|---|
| API Name | s_c__Pos_Layout_Field__c |
| Label | POS Layout Field |
| Plural Label | POS Layout Fields |
| Type | Custom Object |
Fields
| Field Label | API Name | Type | Required | Description |
|---|---|---|---|---|
| Display Name | s_c__Display_Name__c |
Text(255) | No | Label shown for this field and defaults to the field name in sentence case if left blank. |
| Field Name | s_c__Field_Name__c |
Text(255) | No | Salesforce field API name to display. Must be a valid field on the object associated with the layout. |
| POS Layout | s_c__Pos_Layout_Id__c |
Lookup (s_c__Pos_Layout__c) | No | The Layout to which this field belongs. |
| POS View | s_c__Pos_View_Id__c |
Lookup (s_c__Pos_View__c) | No | When set, renders this POS View template in place of the field value. The current record is passed as a drop to the Liquid template. |
| Position | s_c__Position__c |
Number(8,0) | No | A number to determine the order of fields on the layout. |
| Type | s_c__Type__c |
Picklist | No | Controls visibility, indexing, and searchability of the field. Value is a colon-delimited set of tokens (e.g. Visible:Indexed:Searchable). Defaults to field (legacy value equivalent to Visible:Indexed:Searchable). See Type tokens below. |
| StoreConnect External ID | s_c__sC_Id__c |
Text(36) | No | StoreConnect External ID, do not modify in Salesforce |
Relationships
| Field | Type | Related Object | Relationship Name |
|---|---|---|---|
s_c__Pos_Layout_Id__c |
Lookup | s_c__Pos_Layout__c | POS_Layout_Fields_POS_Layout |
s_c__Pos_View_Id__c |
Lookup | s_c__Pos_View__c | POS_Layout_Fields_POS_View |
Type tokens
The Type field accepts a colon-delimited string of tokens that combine to control how the field behaves in the POS. Tokens are case-insensitive.
| Token | Effect |
|---|---|
Visible |
The field is rendered in the layout. Omitting Hidden produces the same effect — explicit use is optional. |
Hidden |
The field is loaded but not displayed. The data is still available for sorting, filtering, Liquid templates, and searches. |
Indexed |
The field is added to the browser’s IndexedDB for fast client-side lookups. Only applies to list and grid layouts. |
Searchable |
The field is included in full-text keyword searches. Only applies to list and grid layouts. |
The legacy value field (or a blank value) is equivalent to Visible:Indexed:Searchable and remains the default.
Examples:
| Value | Behavior |
|---|---|
field (or blank) |
Visible, indexed, and searchable — the default |
Visible:Indexed:Searchable |
Explicit modern equivalent of field |
Visible:Indexed |
Visible and indexed, but excluded from keyword search |
Hidden:Searchable |
Not displayed, but included in keyword search results |
Hidden:Indexed |
Not displayed, but loaded into IndexedDB for filtering |
:::note
Indexed and Searchable tokens are ignored on record and form layouts — they only take effect on list and grid layouts.
:::
Was this article helpful?
Thanks for your feedback! It helps us improve our docs.