Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Fields in PWR apps represents represent what the columns represent in relational databases. It can store data values which that are required for a particular object in a record. Fields can store many different types of data.

...

(C) Audit Fields

The above-mentioned fields explain are as follows:

Standard Field:

Name:

Name The name is a standard field in every object and the field gets created at the time of the creation of the 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 objectobjects.

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 used 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 objects and the object under categorized into 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 the operator is used to check whether an object is an instance of a particular class or not.

...

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 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 field is a built-in (non-custom) audit field that is used to record which syncing user created a record. You can not update that field once the 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 the 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.

...

Is deleted field is used to keep the record of deleted records. If the user delete 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 does do not get permanently deleted from the database unless TTL (Time To Leave) field is applied.

Erase On:

When any of the record has records have been deleted from the org its it gets reflected in the Erase On the field. The restore limit for the Erase On field is of 30 days.

...

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 objectobjects. 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, what different type it should be (such as number, text, date, or pick list).

...