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 2 Current »

Using Field Manager, Object & field schema could be defined and managed.

Common info. to be filled for each Field:

  1. Label

  2. Name

  3. Help Text

  4. Description

  5. Access features

    1. Queryable: This is used for querying the data. This is default set to true.

    2. Creatable: If a field is creatable true, then user will be able to create data for particular field. This is default set to true.

    3. Editable: If editable is set to false, then user will not be able to edit the created field. This is default set to true.

Types of fields:

  1. Address: Allows users to enter address

  2. Array: Allows users to store arrays or list or multiple values into one key.

    1. Fields:

      1. Required: To make it a mandatory field.

      2. Minimum Length: To set minimum array length

      3. Maximum Length: To set maximum array length

  3. Object: Allows users to store embedded documents.

    1. Field:

      1. Required: To make it a mandatory field.

  4. Lookup: Allows users to create a relationship that links this object to another object.

    1. Fields:

      1. Required: To make it a mandatory field.

      2. Unique: Can be used to identify the record based on the uniqueness of the field value. Duplicate records are not allowed.

      3. Relates To: Relation with Object.

      4. Value key: This is the field value which gets stored in the database.

      5. Label Key: This is the field label which gets displayed to the user.

      6. Is Tightly Coupled: This is to establish coupling between objects. For e.g.: Account Object has lookup field ‘relates to’ Contact. If Account record is deleted, will in return delete Contact record.

      7. Child Relationship Name:

      8. Criteria: Used to filter records based on the criteria set.

  5. Checkbox: Allows users to select a True (checked) or False (unchecked) value.

  6. Currency: Allows users to select currency.

    1. Fields:

      1. Currency Selectable: If checked, will enable the currency picklist for the user. Else, user will not be able to modify the currency set.

      2. Minimum: For user to set minimum value of currency

      3. Maximum: For user to set maximum value of currency

  7. Date: Allows users to enter a date or pick a date from a popup calendar.

    1. Fields:

      1. Minimum date: For user to set minimum date value.

      2. Maximum date: For user to set maximum date value.

      3. Date format: Picklist of multiple date formats.

      4. Default Value: For the user to set the default date value.

      5. Sortable: If set to true, enables record sorting in table and list view.

  8. Date/Time: Allows users to enter a date and time.

    1. Fields:

      1. Minimum date/ time: For user to set minimum date/ time value.

      2. Maximum date/ time: For user to set maximum date/ time value.

      3. Date/ time format: Picklist of multiple date/ time formats.

      4. Default Value: For the user to set the default date/ time value.

      5. Hour Clock: Allowed values: 12Hr, 24Hr

      6. Sortable: If set to true, enables record sorting in table and list view.

  9. Duration: Allows users to enter duration.

    1. Fields:

      1. Minimum Time: For user to set minimum time.

      2. Maximum Time: For user to set maximum time.

      3. Time Format: HH:MM; HH:MM:SS

  10. Time: Allows users to enter a time.

    1. Fields:

      1. Minimum Time: For user to set minimum time.

      2. Maximum Time: For user to set maximum time.

      3. Hour Clock: 12 Hr, 24 Hr

      4. Default Value: For the user to set the default time value.

  11. Email: Allows users to enter an email address.

    1. Fields:

      1. Default Value: For the user to set default email value.

      2. Unique: Can be used to identify the record based on the uniqueness of the field value. Duplicate records are not allowed.

  • No labels