Overview

Record Type Model solely focuses on storing and managing data from Salesforce as well as few other CRM objects. Basically, it handles data retrieval and storage for objects.
The model further can be bound to various components like Form, Table, or Repeater, allowing efficient data display and interaction across different layouts.

Let’s explore the screens that follow, after clicking on Model Creation + button.

Reference: How to create a Record Type Model?

Details

In this tab, user can specify the object and its details, on whose basis model is to be created.

Attributes	Description
Type	Allows to specify the type of model, such as: API: For integrating with external applications via REST APIs. Record: For managing Salesforce & few other CRM object data. Note: By default, `Type` is set as `Record`.
Connection	Provides the ability to select records from various connected CRMs with an object structure similar to Salesforce. This feature enables seamless data integration by specifying the desired CRM connection. Note: Currently, noKodr supports Connection only for `Zoho CRM` & `Monday CRM`.
Record Count	Select the record count type for the model: single: For storing a single record of a specific object. multirecord: For storing multiple records of a specified object. Note: By default, Record count is set as `multirecord`.
Object	Allows to specify the object for which you want to create the model and display data. Includes two radio buttons, allowing the user to either select the object from a list or manually enter the API name. The `Select` option lets users choose the object for the model, while the `Enter Name` option enables manual entry of the API name, avoiding the need to scroll through the picklist and specifying the exact object efficiently. Note: By default, radio button is set as `Select`.
Label	Allows to specify the name of the model.
Name	Allows to provide unique API name for the model.
Offset	Allows to specify desired records from bunch of records. For example, suppose for `Contact` object, where a user has `100` records but wants to create a model starting from the `51st` record, the `Offset` can be set to `50`. This allows the model to begin from the specified point, skipping the first `50` records.
Limit	Allows to define the maximum number of records to retrieve from the selected object.
Order By	Allows to choose the field by which to sort the records retrieved from the selected object. Reference: Order By
Do Not Auto Query	If checked, the model will not automatically query or retrieve data from the selected object.

Order By

In Salesforce, there’s no guarantee of the order of results unless you use an Order By clause in a query. Thus, we need to specify Order By to have specific records under consideration.

Specifies whether the results are ordered in ascending (ASC) or descending (DESC) order. Default order is ascending.

Order By Attribute	Description
Field Name	Allows to specify field name which determines the sorting order of the query results.
Sort As	Allows to specify whether the results are ordered in Ascending or Descending order. Note: By default, `Sort As` is set as `Ascending`.

Fields

In this tab, user can view the fields for your selected object. The user can select and add these fields for use in various areas, such as in:

Form Component
Table Component
Repeater Component
Workflow Actions

Note: If you use any model fields in the components mentioned above, in workflow actions, or in criteria such as conditional visibility, disability & read-only settings, or required fields, ensure that the field is added to the highlighted selection panel below.

UI Fields

Note: This tab is only visible when Object for the model is specified.

In this tab, whenever you want to display a value in a field based on certain values entered in other fields, and you desire to exhibit this on the UI in real-time without saving the record in objects, UI Fields helps you with achieving the requirement.

For example, Upon entering the first name and last name, if you desire to display the full name on the UI by concatenating these two fields without saving the record first to preview the appearance, you can utilize the UI field for this purpose.

When creating a UI Merge field, you need to provide the following details:

Attribute	Description
Label	Allows to specify the name of the field.
Name	Allows to provide unique API name for the field.
Merge Text	Allows to specify the fields whose values you want to display. You can include multiple fields and perform operations such as concatenating field values or performing mathematical operations like addition and subtraction. Note: You can source merge text not only from model fields but also from various other sources, such as: Models Various Local Storage Key Cookie Key, etc.

Merge Text

Merge text is a key feature of the noKodr application, allowing users to display field values on the UI. Depending on the data type, users can perform mathematical operations on these fields.

For example, if you want to display a calculated total price based on the quantity and unit price entered by the user on a sales order form, and you wish to dynamically showcase this on the UI without saving the record in the database, you can achieve this using the UI fields in noKodr.

After selecting merge text you can you can see several options such as:

Attribute Name	Description
Source Type	In this option, you can select various sources from which you want to display values.
Value	The available options will change depending on the selected source type. For example, if you choose "Static" as the source, you can provide a fixed static value.
Merge Field Expression	The selected field from the source will be displayed in a merge format. For instance, the first name field from the contact model will appear as: {model:contact.FirstName}.
Message Body	In this option, You can add multiple values to form your final UI merge text. For example, merge fields include {model:contact.FirstName},{model:contact.LastName} will eventually display the contact's first name and last name next to each other.

Available Sources

After clicking on the Gear Icon, you can select various sources to include fields or values, such as variables, other models, static values, etc.

Source Type	Description
Static	Use this option to provide a fixed static value.
Field	Select the field from the chosen object in the model whose value you want to include.
Model	Choose the field from other models whose value you want to include.
Variable	Select from the variables created in the layout whose value you want to use.
Cookie Key	Choose the available cookie key whose value you want to include from your browser.
Local Storage Key	Select the available Local Storage Key whose value you want to include from your browser.
User	You can also select fields from the current logged-in user in your organization to include in the merge. Note: The User source refers to the currently logged-in user in your organization. This means that if you include the First Name field from the user, each time a different user logs in, they will see their own First Name displayed.

After selecting the source type, you need to choose the available options based on the selected type. For example, if you have selected "Model" as the source type, you will need to select one model from the available models.

Note: Only single record models are visible here and can be used in the merge text. Multi-record models are not supported here.

Once you select a model, the field options will become available. You can then choose the fields you want to include in your merge field expression and combine multiple fields to form your final expression in the message body.

For more information, you can click on this link to configure UI Fields.

Criteria

In this tab, you can specify the filter criteria to retrieve the specific records from selected objects

For example, If you want to display contact records that do not have an assigned account, you can set a filter where AccountId equals NULL. This filter will query all contacts where the account field has a null value.

Above image shows various attributes such as:

Attribute

Description

Field

Allows you to select a field from a model based on the chosen object, helping you to define criteria using model fields.

Operators

The available operators will depend on the type of field selected, allowing you to set the criteria accordingly.

Reference: Filter operator

Source Type

Allows to choose from several options to compare values with the selected field. The available options include:

Static
Model
Variable
User
Null
Blank

Filters Attributes

Filter Operators

Operator	Supported Field Types	Description
Equal	Number, Currency, Date, Text, Boolean, Picklist	The equal operator is used to compare two values or expressions. It is used to compare numbers, strings, Boolean values, variables, objects, etc. The result is TRUE if the expressions are equal otherwise it’s FALSE
Contains	Text, Picklist	The contains operator returns TRUE if the value on the left contains the value on the right, and otherwise FALSE
Starts With	Text, Picklist	It returns TRUE if a string or number starts with the specified character otherwise it returns FALSE.
Ends With	Text, Picklist	It returns TRUE if a string or number ends with the specified character otherwise it returns FALSE
In	Text, Picklist	IN operator allows you to easily test if the expression matches any value in the list of values. Determines whether the value of an expression is equal to any of several values in a specified list.

Source types

Source Type	Description
Static	Use this option to provide a fixed static value.
Model	Choose the field from other models whose value you want to compare.
Variable	Select from the variables created in the layout whose value you want to compare.
User	You can also select fields from the current logged-in user in your organization to compare with model field Note: The "User" source refers to the currently logged-in user in your organization. For example, if you compare the contact's First Name field with the logged-in user's First Name, the system will compare the names every time a user logs in. If a match is found, the corresponding contact record will be retrieved; otherwise, no record will be returned.
Null	The Null option will check if the selected model field has no value at all, meaning the field is completely empty and hasn't been populated with any data.
Blank	The Blank option will check if the selected model field has been populated with a blank or empty value, such as an empty string. For example, when a text field contains no characters but is still considered "filled" with an empty value or empty string.

Record Type Model