Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 4 Next »

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 Field:

There is one standard field in every Custom object and the field get created at the time of creation of object. This is cannot be deleted or edited.

For Standard object, the fields which are present by default in them, cannot be deleted from standard object.

(B) Custom Field:

Custom fields can be create 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 field, we can decide where it appears, what info it contains, what format it should be (such as number, text, date, or pick list) and who sees it and who can change the field value. 

There are 26 types of field data types which we can use to create a different fields:

Address: A compound data type that contains address field 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:

Object:

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 (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 for 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:

Time:

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:

(C) Audit Field:

  • No labels