View source for CRM Objects

CRM objects are pre-defined ''system'' [[object]]s that are built in to the platform. They become available when the Sales Force Automation application is installed. They 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.)

{{Note| Other [[Built-in Objects]] are available, as well.}}

==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 ===

*The following Property options ''are not available in {{Typenolink}}s'':
:*[[Display Styles]] - Only Sectional Layout and Horizontal Tabbed Layout are supported for CRM Objects. No Display Styles are available for Built-In Objects.
:*[[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

=== Searches Use Uppercase Tags ===
Note that when you do a Dynamic Search of these records, fields are returned with tags that are all-uppercase, with underscores. For example: <tt><nowiki><OWNER_ID></nowiki></tt>. When specifying criteria for search, those names must be used.

When you do an HTTP GET, on the other hand, tags are returned in lowercase, with underscores, as shown in the tables on this page. For example: <tt><nowiki><owner_id></nowiki></tt>. Those tags are also used in an HTTP PUT.

{{Note||In some cases, field names have other differences, as well. Return all fields in a GET or SEARCH to confirm the field names, or consult the tables below.}}

=== 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}}''  fields opens the record for viewing
::*By contrast, {{Type|}}s provide a ''Details'' link to open the record for viewing

==CRM Object Type Identifiers==
{{:CRM Object Type Identifiers}}

==CRM Object Attributes==
{{:CRM Object Attributes}}