You need to sign in to do that
Don't have an account?
prashanth murukonda
Why Custom Settings in Salesforce
Why Salesforce introduced CustomSettings instead we have CustomObjects?
function readOnly(count){ }
You need to sign in to do that
Don't have an account?
Custom Settings vs. Custom Objects
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.
So if Custom Settings are so limited, why use them?
Avoiding Governor Limits
Depending on how your Apex code interacts with Custom Settings, they can have zero impact on certain governor limits. That’s right – you can retrieve all of the values in a Custom Setting with absolutely no impact on the governor’s count of the number of queries you’ve performed or the number of rows you’ve retrieved. This makes Custom Settings particularly useful for reference data, like lists of Postal Code / State mappings.
There are a few caveats, however. First, you have to query the Custom Setting in a very specific way in order to take advantage of this “no governor limit” feature. Specifically, you have to use the Custom Setting’s GET methods, not SOQL, to query for data. See the Apex Language Reference for more information. Second, other governor limits, like those on heap size and number of script statements, do still apply. Even with these caveats, though, Custom Settings can provide a welcome relief from the limits on queries and rows.
1) http://www.infallibletechie.com/2013/04/custom-settings-in-salesforce.html
Let us know if this will help you