View source for Built-in Objects

Built-in objects are pre-defined [[object]]s that come with the platform. [[Project]] objects become available when the Project Management Application is installed. The other built-in objects are always available.

Built-in objects are customizable, but some functionality is fixed. ({{Type|}}s, in contrast, are created by platform developers. They are fully configurable, and become available when custom applications are developed or installed.)

==For Developers==
[[Service Provider]]s should consider the characteristics of {{Type|}}s vs [[CRM Objects]] and [[Built-in Objects]] when building applications. {{Type|}}s are more customizable and generally more flexible, but the [[CRM Objects]] and [[Built-in Objects]] may have special functionality that is desirable.

{{Tip|The [[CRM Objects]] and [[Built-in Objects]] are due to be replaced by newer, more customizable versions in a future release. To minimize any impact on your applications, prefer  {{Type|}}s, if at all possible.}}

:''Note'': Some objects will be displayed as tabs in the application, while others are hidden from view

=== Property Limitations ===
:[[File:Customizeobjects-sysgen.gif|none|thumb]]
*The following Property options ''are not available in {{Typenolink}}s'':
:*[[Display Styles]] - Only Sectional Layout and Horizontal Tabbed Layout are supported
:*[[Record Locators]] can not be changed
:*Cannot make an object Active or Inactive
::*Inactive objects are not used in an application
::*Data in an Inactive object cannot be viewed, edited or deleted
:*Cannot set the object to be ''Web Enabled''; exception: [[{{leadprospect}}]]s can be ''Web Enabled''
::''Note:'' Web Enabled objects can use the [[Web Forms]] tool
:*The Help URL is set by default, and cannot be changed
:*Campaign Tracking is enabled by default, and cannot be changed

=== REST Searches Use Uppercase Tags ===
{{:REST Searches Use Uppercase Tags for Standard Objects}}

=== Other Considerations ===
*[[Object Inheritance]] is not supported
*[[Lookup]] fields to {{Typenolink}}s do not include Record Selection Criteria or Post-selection Javascipt
*[[Workflows]] are not supported
*{{Typenolink}}s cannot be deleted, but can be hidden from view
*Fields associated with the [[Record Id]] are clickable in {{Typenolink}}s
:*Clicking the link to an ''Account Name'', ''Contact Name'', or other ''{{Typenolink}}s'' opens the record for viewing
:*By contrast, {{Type|}}s provide a ''Details'' link to open the record for viewing

==Built-in Object Type Identifiers==
{{:Built-in Object Type Identifiers}}

==Built-in Object Attributes==
{{:Built-in Object Attributes}}