Fields in PWR Apps represent what the columns represent in relational databases. It can store data values that are required for a particular object in a record. Fields can store different types of data.
There are 3 types of fields:
(A) Standard Fields
(B) Audit Fields
(C) Custom Fields
Standard Field:
Name:
Name is a standard field in an object this gets created at the time of the creation of the object.
Tags:
Using this field the user can give a tag to the record of an object from the list of values. Users can create new tags at run time as well.
Standard and Audit fields cannot be edited or deleted.
Audit Field:
Record Id:
A record id can help you identify a record in the database. Each record has a unique id which is known as the record id. It is system generated and cannot be edited or deleted.
Object Type:
We have a common collection (or object) for all the records created under the custom object. Object type contains the object name (custom object name) for which the particular record is created.
Instance:
This field contains the instance for which the record is created.
Owner:
Objects have an owner Id field that is a reference to the user who owns that record. Ownership is an important concept that affects the security model and has other implications throughout the system.
Created By:
This is the reference to the user who created that record.
Created On:
This field has a date and time at which the record is created.
Last Modified by:
This is the reference to the user who modified the record last time.
Last Modified On:
The last modified date refers to the last time a document or media file was modified. This information is gathered from metadata within the document or from the website's servers.
Is Deleted:
Is deleted field is used to keep the record of deleted records. If the user deletes any record from the account then with the help of the “Is Deleted” field we can keep the track of deleted records in the database.
The deleted records do not get permanently deleted from the database unless TTL (Time To Leave) field is applied.
Deleted By:
Deleted by field is a built-in (non-custom) audit field used to record which syncing user deleted a record.
Deleted On:
Deleted on is a field where date refers to the last time a document or file was deleted.
Is Test Record:
The field test record is used by the developer to maintain the test record.
Erase On:
When any of the records have been deleted from the org it gets reflected in the erase on the field. The restored limit for the erase on the field is of 30 days.
Is Published:
Once you publish an object, you can select which individual fields on that object are published. For standard objects that are published, a default set of fields is automatically published.
Is Manageable:
Is Manageable is a Boolean field of metadata object that is used to make an object is managed or
un-managed.
Custom Field:
Custom fields can be created on standard or custom objects. they may or may not be required.
The custom fields are added by the administrator or developer to meet the business requirements of your organization.
When we create a custom or standard field, we can decide what different type it should be (such as number, text, date, pick list, etc).
How to create a custom field:
From Profile, go on “Setup”
Click on “Schema” and select a “Objects” option
Click on any Object where we have to add the fields
Click on “New” and select the appropriate data type to create a field
There are 26 data types that we can use to create a different field
Steps to configure:
Goto Component section
Search and select the field component
Drag and drop the field component in the layout
...
Overview
The Field is a generic component using which you can accept values in different formats and data types
e.g. number, phone, email, text, etc
It can be bound with the model Field and variable
If you want to accept/display data to the user without an object you can use the Field component
Attributes
Label
The label is a short description of the field that will be displayed before the data input/output
Placeholder
A placeholder is a short text, located inside the input data field
...
Layout
It is a design using which the user can arrange the fields
The Layout comes in 5 different forms:
Stacked: In a stacked layout, the input/output field is under the field label with a small margin around the label, and the input/output field
Horizontal: In a horizontal layout, the input/output field is in front of the field label with a small margin around the label, and the input/output field
Single Column: A Single Column layout is the same as a horizontal layout the only difference is the input/output field size is greater than the field label in a layout
No Label: In the No Label layout, the label name is not visible only the input/output field is present in the layout
Compact: Compact layout is the same as a stacked layout, the difference is there is no margin around the label and the input/output field
...
URL to create a field as a link
This feature is used to make a field a hyperlink field
This value will serve as a hyperlink text
Inline Edit
The inline edit feature allows us to edit the record without pressing the edit button
Debounce Time in seconds
Debounce Time is the time taken to complete the two actions
e.g. When you click on the save button, the time it takes to complete the save action is debouncing time
Validations
Required Type: Ensures that a specific type of input is required.
Required Error Message: Specifies the error message to be displayed when the required type is not provided.
Minimum Length: Specifies the minimum length of input required.
Min Length Error Message: Specifies the error message to be displayed when the input length is less than the minimum required length.
Maximum Length: Specifies the maximum length of input allowed.
Max Length Error Message: Specifies the error message to be displayed when the input length exceeds the maximum allowed length.
Pattern: Specifies a pattern or format that the input must adhere to.
Pattern Error Message: Specifies the error message to be displayed when the input does not match the specified pattern.
Read-only:
Never: The field cannot be read-only
Always: The field will be always read-only
Conditional: Depending on the read-only criteria, the field can be set as read-only or not
Disable:
Never: The field cannot be disabled
Always: The field will be always disabled
Conditional: Depending on the disability criteria, the field can be set as disabled or not