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
Configuration of a Field component:
...
Name: A name is a combination of a field name and an instance name as the prefix. This field is non-editableName is the unique identifier of the component in the layout
Label: The text that is inserted into the component of the field is known as the label. Users can change the field label
Show Horizontal line: By checking this checkbox, the user will be able to view the horizontal line in view mode
Placeholder: A placeholder is a text, located inside a field. It is an additional hint, description, or example of the information required for the field. The Placeholder text is editable
Field Type: It is a type used to create a field
Layout: It is a design through which the user can arrange the fields. The Layout options are arestacked
Stacked: The stacked layout allows the vertical arrangement of the field label and
placeholder
Horizontal: The horizontal layout allows the horizontal arrangement of the field label and
placeholder Single Column: A Single Column layout is arranged as columns, with all heights being equal (This works the same as horizontal but the distance between field label and placeholder is minimized)
No Label: In the No Label layout, the label name is not visible
Compact: Compact arrangement allows to arrange fields compact i.e., without having any space around
Hide Space: Using this checkbox, the user can hide spaces on 3 sides of the field i.e., left, right & bottom
URL to create a field as a link: user can enter a URL and make the field as a hyperlink.
Is Clickable: If URL is available as a link in a field, then this checkbox can be used to make the field clickable or non-clickable
Inline Edit: This checkbox allows the user to edit the field directly in view mode
Debounce Time in seconds: Debounce Time is the interval that must pass before calling the next action
Value Destination Type: This attribute decides if the user wants to save a value in a variable or model
Value Destination Variable: From the value destination variable, the User user can choose the variable in which he/she the user wants to save the value of the power apps field field
Value Destination Model: From the value destination model, the User user can choose the specific model in which he/she the user wants to save the value of the power apps field field
Component Size: The user can modify the size of the component in the layout layout as per grid size
Margin Location: Defines the position of the margin for a field. It is applicable to around, top, left, bottom, right, horizontal, vertical vertical
Margin Size: The margin size of view can be set to none, xxx-small, xx-small, x-small, small, medium, large, x-large, xx-large large
Style: Styles described Style describes how fields should be rendered in preview mode. Users need to create one cdn link from the CSS tab on the layout designer page to use the style style
Classes: Classes are used to apply unique styling and formatting to the fields in preview mode. Users need to create one cdn link from the CSS tab on the layout designer page for using classes classes
Visibility Type: Specifies whether the field is visible or not not
Always: The field is always visible visible
Conditional: Visibility of a field depends on the given condition or criteria criteria
Required Type:
Never: The field is not required required
Always: It must be a mandatory field field
Conditional: Depending on the required criteria, the field can be set as required or not
Required Error Message: The user can enter a custom error message for the required field
Show Success Message: Using this checkbox, the user can show a success message
Success Message: The user can enter a success message when the show success message checkbox is true true
Show Error Message: Using this checkbox, the user can show an error message on the layout layout
Error Message: The user can enter an error message when the show error message checkbox is true true
Read only Type:
Never: The field cannot be read-only
Always: The field is always read-only
Conditional: Depending on the read-only criteria, the field can be set as read-only or not
Disability Type:
Never: The field cannot be disabled disabled
Always: The field can be disabled disabled
Conditional: Depending on the disability criteria, the field can be set as disabled or not not