Fields in PWR apps represents what the columns represent in relational databases. It can store data values which are required for a particular object in a record. Fields can store many different types of data.
There are 3 types of fields:
(A) Standard Fields
(B) Custom Fields
(C) Audit Fields
The above mentioned fields explain are as follows:
Standard Field:
Name:
Name is a standard field in every object and the field gets created at the time of creation of object. This is cannot be deleted or edited.
For standard objects, the fields which are present by default in them, cannot be deleted from standard object.
Audit Field:
Record Id:
A Record ID can help you identify a record in the database. Each record in system has a unique ID field assigned to it which is known as Record ID. It is system generated and cannot be edited or deleted. It is generated every time a new record is inserted into the application.
Object Type:
It is use for dynamic references to retrieve information about an object through Object Type.
For example, inst0526__manualTesting : here the records under categorized into Manual testing object and the object under categorized into Instance.
Instance:
If you do something at someone's instance, you do it because they have ordered or requested you to do it. The instance of operator is used to check whether an object is an instance of a particular class or not.
Owner:
Objects have an owner Id field that is a reference to the user who owns that object. Ownership is an important concept that affects the security model and has other implications throughout the system. Any user can query the owner field for any record they can access.
Tags:
A Tag field on a Content Type allows Content Contributors to label the content with keywords (tags) as it the content is contributed. Each Content Type can only have one Tag field. You can tag any field-value pair directly from the results of a search.
Created By:
Created by field is a built-in (non-custom) audit field is used to record which syncing user created a record. You can not update that field once record is created.
Created On:
Created on is a field where date refers to the last time a document or media file was created. You can not update that field once record is created.
Last Modified by:
The date and timestamp for changes made to an individual record, including the User who made the change. Unfortunately you won't be able to change the "last modified by" field, as this is a system field that is read only.
Deleted By:
Deleted by field is a built-in (non-custom) audit field is used to record which syncing user deleted a record.
Deleted On:
Deleted by is a field where date refers to the last time a document or file was deleted.
Last Modified On:
The "Last Modified On" 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 Test Record:
The field “Is Test Record” is used by the developer to maintain the test record.
Is Deleted:
Is deleted field is used to keep the record of deleted records. If the user delete any record from the account then with the help of “Is Deleted” field we can keep the track of deleted records in database.
The deleted records does not get permanently deleted from the database unless TTL (Time To Leave) field is applied.
Erase On:
When any of the record has been deleted from the org its gets reflected in the Erase On field. The restore limit for the Erase On 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 used to make an object is managed or
un-managed.
Custom Field:
Custom fields can be created on Standard or Custom object. They may or may not be required.
The Custom fields which 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 where it appears, different type it should be (such as number, text, date, or pick list).
How to create a 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 a “New” and select the appropriate data type to create a field
There are 26 data types which we can use to create a different fields:
Address:
A compound data type that contains address data. This field includes few sub-fields are as follows:
Country: The country detail for the address.
State: The state for its territory, the area of jurisdiction or geographic boundaries for the address.
City: The city is a place in which people live and work; its detail for the address.
Street: The street address includes address of a building, typically comprising a house number, street name detail.
Postal Code: The postal code refers to the code in the post office number of the postal code system for the address. Postal codes are usually assigned to geographical areas.
Array:
An array is a systematic arrangement of similar objects, usually in rows and columns. Arrays are used to store multiple values in a single variable, instead of declaring separate variables for each value.
Object:
Object is a field, where variables are saved together within an object, we call them fields or member variables.
Lookup:
A lookup relationship essentially links two objects together so that you can “look up” one object from the related items on another object. Lookup fields allow users to associate two records together in a relationship but has no effect on deletion or security.
For example, a user can associate a contact record to an account record using the Account Name lookup field. When users edit a lookup field, they need to find the right record to associate.
Lookup relationships can be one-to-one or one-to-many or many-to-many
In a one-to-one relationship, one record in a table is associated with one and only one record in another table. For example, in a school database, each student has only one student ID, and each student ID is assigned to only one person.
In a one-to-many relationship, one record in a table can be associated with one or more records in another table. For example, each customer can have many sales orders.
A many-to-many relationship occurs when multiple records in a table are associated with multiple records in another table. For example, a many-to-many relationship exists between customers and products: customers can purchase various products, and products can be purchased by many customers.
Checkbox:
A checkbox (Tick box) is a graphical widget that permits the user to make a binary choice between one of two possible options.
If the user may have to answer “Yes” its ‘Checked’ or “No” its ‘not Checked’ on a simple yes/no question. We can set a default value is either yes/no.
The Checkbox field have feature accessibility like may or may not be Read-only or Sort-able, Create-able or Editable.
Currency:
Currency fields contain currency values. The currency field exists only for those organizations that have enabled multi currency support.
The currency field have feature accessibility like may or may not be Required, Select-able, Read-only or Sort-able, Create-able or Editable. We can choose appropriate currency type from drop down whichever listed and may apply the limitation to be taken as minimum or maximum on currency.
Date:
Allows users to enter a date or pick a date from a popup. Use the functions DAY( date ), MONTH( date ) and YEAR( date ) to return their numerical values. This field will store the text version of Date Field in dd/mm/yyyy format.
A Date value stores a year, month, and day. A date field is great for showing the birth date.
The date field also have feature accessibility like may or may not be Required, Select-able, Read-only or Sort-able, Create-able or Editable
Date/Time:
A Date/Time value stores a year, month, day, and a time. The time is stored as GMT, but displays in the time zone of the user viewing it. It’s important to keep time zone conflicts in the back of your mind as you work with Date/Time values in formulas.
This field is come along with multiple date and time format. We can pr-defined date as minimum and maximum by applying validation.
The date/time field also have feature accessibility like may or may not be Required, Select-able, Read-only or Sort-able, Create-able or Editable
Duration:
The duration field type is a numeric field type intended for use with time duration measured in hours, minutes, seconds, or milliseconds. Depending on the format of the duration field, the values are either stored as an integer or decimal representing a number of seconds.
Time:
The time type is useful for time management, event planning, and project management.
You can select the time field type when you create a custom field. The time type is a timestamp without the date included.
Use the time field type when you require a time of day that isn’t specific to a single date. For example, use it to display business hours, or if you want to compare times of the day to calculate a duration.
Image:
Image Field is a file field with uploads restricted to image formats only. Before uploading files, one needs to specify a lot of settings so that file is securely saved and can be retrieved in a convenient manner.
Image Field is used for storing valid image files into database in jpg, jpeg, jpg, svg and gif format. Also, allowing multiple sources to use like attachment, record and URL.
Email:
This is a separate fields to record email details from a user, called the E-mail field data type field. This field can validate if the given email ID is valid or not.
This field allows users to enter an email address, which is validate to ensure proper format.
Integer:
Integer fields are fields in which you can make number entries and if required also use the values for calculations.
The minimum value permitted. The user can enter a value that is equal to the minimum value. Or else, the user must enter the value greater than the minimum value.
The maximum value permitted. The user can enter a value that is equal to the maximum value. Or else, the user must enter the value less than the maximum value.
Default value must be between the minimum and the maximum value.
Double: (bug: Unable to apply validation; Min n Max limit validation is not applicable)
Double is a field where we can make number entries with decimal places.
The user can enter a value that is equal to the minimum value. Or else, the user must enter the value greater than the minimum value.
The user can enter a value that is equal to the maximum value. Or else, the user must enter the value less than the maximum value.
Default value must be between the minimum and the maximum value.
Multi-select:
The multi-select pick list data type field contains many of the data available on the list. This pick list can allow users to select multiple data from the list.
Multi-pick list fields allow you to select multiple values on your records for various use cases. You have the ability to define values on creation of the field and after creation you can continue to add and remove other values.
Percentage:
The Percent is a field that allows users to enter a percentage number as a decimal. The percent field type is a field type designed to hold numerical values formatted as percent. The values in a percent field are all represented as fractions of 100 with the percent sign.
e.g. the number . 75 in a percent field is represented as 75%.
Phone:
The Phone field enables your users to enter a valid international phone number. The input area of the phone field contains: A drop-down menu to select the international country calling code. An input box, with indicative text, to enter the phone number.
Select:
The select field offer a selection of options available for specific fields in a object, such as a list of regions. Users can then choose a single value from a list of options rather than make an entry directly in the field, which cuts down on errors and helps keep data clean.
Text:
Allows user to any combination of letters and numbers.
They typically appear in forms and dialog. Text field component design should provide a clear affordance for interaction, making the fields discoverable in layouts, efficient to fill in, and accessible.
Tags:
A Tag field on a Content Type allows Content Contributors to label the content with keywords (tags) as it the content is contributed. Each Content Type can only have one Tag field. You can tag any field-value pair directly from the results of a search.
Radio button:
Radio buttons are arranged in groups of two or more and displayed on screen as, for example, a list of circular holes that can contain white space (for deselected) or a dot (for selected). Each radio button is normally accompanied by a label describing the choice that the radio button represents.
The choices are mutually exclusive; when the user selects a radio button, any previously selected radio button in the same group becomes deselected (making it so only one can be selected). Selecting a radio button is done by clicking the mouse on (or touching the screen over) the button, or the caption, or by using a keyboard shortcut.
Text Area:
Text area field represents a multi-line plain-text editing control, useful when you want to allow users to enter a sizable amount of free-form text, for example a comment on a review or feedback form.
We can customize the field by applying the validations like maximum & minimum limit, number of rows & columns and the direction and pattern of the field area.
Rich Text Area:
In the Rich Text Area, with the use of a toolbar users can format the field content and add images and hyperlinks.
The toolbar allows the users to undo, redo, bold, italic, underline, strike-out, add a hyperlink, upload the image, modify alignment add a numbered or non-numbered (bulletin) list.
URL:
The URL field enables your users to enter a URL (Uniform Resource Locator) - the link to a website or web page.
You can edit the field properties and set a default pattern for the URLs of the entries of a specific content type.
Merge Text:
Your template content can store fields that show field values from different objects. These merge fields are automatically updated in your content when the referenced field is updated on the other object. This process is useful if you want template content to reflect changes made elsewhere in your org.
Formula:
Formula field is used to calculate custom fields, validation rules, Flow logic etc.
Formula field are read-only fields that automatically calculate a value based on other fields or a formula. Any change in expression or formula will automatically update the value of formula field.
A formula field can reference the value of another custom or standard field using a merge field.