View source for Fields

'''Designer > Data > Objects > {object} > Fields'''

Fields are attributes of a {{Type|}}, and are used to contain many types of data:
*Fields are defined by giving them a label and specifying a [[Field Display Types|Field Display Type]]
*New fields can be added to the [[Form]] canvas
*Fields can have [[#Role-Based Field-Level Permission Control|Role-Based Visibility]], meaning that the field data is visible only to users who have permission rights for that field
*Fields can have a [[Default Value]] defined, which pre-populates the field in the data entry form ([[Form]])
:* Default values can be created with [[Formula Fields]]
*Fields created by Users are listed as Custom in the ''Type'' column


{{Permissions|Customize Objects|edit Fields}}

==Add Fields==
Fields can be added to an [[Object]] from the Fields tab. The fields that are displayed to users in different roles, and the positioning of those fields, is defined in [[Forms]]. 

===Add a Field from the Fields Tab===
{{:Add Field}}

==Delete a Field==
'''To remove a field from a Form:'''
#Click '''Designer > Objects > {object}'''
#In the Forms tab, hover the mouse over the field to remove
#Click the Remove Field icon [[File:delete.gif]] in the floating toolbar 
#:[[File:Draggablefieldicons.gif|none|thumb]]

The field is removed from the layout, but it remains available in the object and is moved to the ''Pick Existing'' section of the [[Elements Sidebar]]. Fields can be reused in this layout or any new layouts.

'''To delete a field entirely:'''
{{:Delete a Field}}

==Field Audit Log==
{{:Field Audit Log}}

==Role-Based Field-Level Permission Control==
{{:Role Based Permission Control}}

==For Developers==
Visit these pages for a list predefined fields in
:* [[CRM Objects]]
:* [[Built-in Objects]]

===Guidelines for Add/Update Field Value===

The Order of precedence of field properties (#1 takes precedence over #2, etc.):
#[[Fields#Add_a_Field_from_the_Fields_Tab|Always Required]]
#[[Fields#Role-Based_Field-Level_Permission_Control|Field Visibility]]
#[[Fields#Field_Display_Attributes|Display Attribute]]

;Add/Update Field Value:

:*For the [[API]]/UI calls, the ''Always Required'' property applies, even if the field is defined as hidden/read only via [[Form]] or [[Field Visibility]] settings
::*Fields defined as ''Hidden/Read-Only'' via Field Visibility settings can not be added/updated from the UI, and should not be added/updated from the API
:*Fields defined as ''Hidden/Read-Only'' via Display Attributes are considered only for UI calls (but not API calls)
::*''Hidden'' Fields can be updated through the scripting
:*Fields defined as part of {{type|}}s can be set to ''Read-Only'' or ''Hidden'' via [[Field Visibility]] settings
;Log Access Violation:
:*When fields defined as ''Hidden/Read-Only'' via Field Visibility settings are used in an API/UI request, the entry can be logged in the [[Audit Log]], provided that the [[Audit_Logs#Enhanced_Security_Audit|Enhanced Security Audit]] is enabled
<noinclude>

[[Category:Objects| 3]]
[[Category:{{features}}]]
</noinclude>