function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion
ramesh babu 114ramesh babu 114 

what is difference between custom object and custom settings

what is difference between custom object and custom settings
Best Answer chosen by ramesh babu 114
Suraj TripathiSuraj Tripathi
Hi Ramesh,

An org will create a custom object when they want to track something completely new in Salesforce.  So you know the standard Account, Contact, Opp, etc.  A custom object would be created for example if you wanted to track Job Applications - since this wouldn't fit in the normal Account/Contact/Opp model!

Custom settings can be seen as simply a "settings" page for applications.  For example, an app might have an on/off button - this would be found in a custom setting.  

So let's say you're creating a dating app in Salesforce.  You'd probably create a custom object: "Banking App" and a custom setting "Only Create verified Account".

Regards,
Suraj

All Answers

sfdcMonkey.comsfdcMonkey.com
Custom settings are similar to custom objects and enable application developers to create custom sets of data, as well as create and associate custom data for an organization, profile, or specific user. All custom settings data is exposed in the application cache, which enables efficient access without the cost of repeated queries to the database. This data can then be used by formula fields, validation rules, Apex, and the SOAP API.

There are two Types of Custom settings 
List Custom Settings : A type of custom setting that provides a reusable set of static data that can be accessed across your organization. If you use a particular set of data frequently within your application, putting that data in a list custom setting streamlines access to it.

Hierarchy Custom Settings :A type of custom setting that uses a built-in hierarchical logic that lets you “personalize” settings for specific profiles or users. The hierarchy logic checks the organization, profile, and user settings for the current user and returns the most specific, or “lowest,” value. In the hierarchy, settings for an organization are overridden by profile settings, which, in turn, are overridden by user settings
More info: http://goo.gl/c7Dv17

   Custom objects are custom database tables that allow you to store information unique to your organization. For custom objects, the custom flag—a Boolean field in the describe results—is true.
Client applications with sufficient permissions can invoke API calls on existing custom objects. You can create new custom objects with the user interface, or by using the metadata WSDL with a client application or using the Force.com IDE.


Difference between Custom Object and Custom Settings 

        In some ways, Custom Settings look very much like Custom Objects. In fact, if you use a tool like the Data Loader to view a list of objects in your org, you’ll see that Custom Settings are listed together with Custom Objects, without any visible distinction between the two. However, while both Custom Objects and Custom Settings allow you to define Custom Fields, there are some important differences.

Limited field types – Custom Settings support only Checkbox, Currency, Date, Date/Time, Email, Number, Percent, Phone, Text, Text Area, and URL field types. Most notably absent are Formula and Picklist, as well as field types that define relationships to other objects, like Lookup and Master/Detail. You can’t create lookups from Custom Objects to Custom Settings either.

No validation rules – You can’t define validation rules on Custom Settings.

No workflow or triggers – You can’t define workflow rules or triggers on a Custom Setting. Any validation of data, update of related records, or other actions that you might use workflow or a trigger to perform for a Custom Object have to be implemented differently for a Custom Setting.

No page layouts or record types – You can’t re-arrange fields on the page layout for Custom Settings. Custom Settings aren’t really intended to be visible to every-day users. If you need them to be, you can create Visualforce pages to allow users to view and manipulate Custom Setting data.

Advantages of Custom Settings over custom object
Avoiding Governor Limits
Hierarchical Access to Data

i hope it helps you.
  Let me inform if it helps you and kindly mark it best answer if it helps you
thanks
Suraj TripathiSuraj Tripathi
Hi Ramesh,

An org will create a custom object when they want to track something completely new in Salesforce.  So you know the standard Account, Contact, Opp, etc.  A custom object would be created for example if you wanted to track Job Applications - since this wouldn't fit in the normal Account/Contact/Opp model!

Custom settings can be seen as simply a "settings" page for applications.  For example, an app might have an on/off button - this would be found in a custom setting.  

So let's say you're creating a dating app in Salesforce.  You'd probably create a custom object: "Banking App" and a custom setting "Only Create verified Account".

Regards,
Suraj
This was selected as the best answer