1. From Setup, enter Custom Settings in the QuickFind box, then select Custom Settings.
2. Click New to create a new custom setting, clickEdit next to the name of a custom setting, or clickEdit while viewing the details of a custom setting.Note A iconindicates that the custom setting is in an installed managed package. You can’tedit or delete a custom setting installed from a managed package.
3. Define the following:Label—Enter the label displayed in the application.Object Name—Enter the name to be used when the custom setting is referenced by formula fields, validation rules, Apex, or the SOAP API. Note Salesforce recommends using ASCII for theObject Name. The name can't exceed 38 ASCII characters. If you use double byte, there are additional limits on the number of characters allowed. Setting Type—Select a type of List or Hierarchy. The List type defines application-level data, such as country codes or state abbreviations. The Hierarchy type defines personalization settings, such as default field values, that can be overridden at lower levels in the hierarchy.Important After you save a custom setting, you cannot change this value.Visibility—Select a visibility of Protected or Public.Protected—If the custom setting is contained in a managed package,subscribing organizations can't see the custom setting: it doesn't display as partof the package list. In addition, subscribing organizations can't access thecustom setting using either Apex or the API, however, developer organizations can.If the custom setting is contained in an unmanaged package, the custom setting isavailable through the Enterprise WSDL like any custom object (as if the Visibility was Public.)Public—The custom setting is available through the Enterprise WSDL likeany custom object. You can package custom settings defined as public. Thesubscribing organizations can edit the values, as well as access them using Apexand the API, regardless of the type of package (either managed or unmanaged).Important After you save a custom setting, you cannot change this value.
4. Label—Enter the label displayed in the application.
5. Object Name—Enter the name to be used when the custom setting is referenced by formula fields, validation rules, Apex, or the SOAP API. Note Salesforce recommends using ASCII for theObject Name. The name can't exceed 38 ASCII characters. If you use double byte, there are additional limits on the number of characters allowed.
6. Setting Type—Select a type of List or Hierarchy. The List type defines application-level data, such as country codes or state abbreviations. The Hierarchy type defines personalization settings, such as default field values, that can be overridden at lower levels in the hierarchy.Important After you save a custom setting, you cannot change this value.
7. Visibility—Select a visibility of Protected or Public.Protected—If the custom setting is contained in a managed package,subscribing organizations can't see the custom setting: it doesn't display as partof the package list. In addition, subscribing organizations can't access thecustom setting using either Apex or the API, however, developer organizations can.If the custom setting is contained in an unmanaged package, the custom setting isavailable through the Enterprise WSDL like any custom object (as if the Visibility was Public.)Public—The custom setting is available through the Enterprise WSDL likeany custom object. You can package custom settings defined as public. Thesubscribing organizations can edit the values, as well as access them using Apexand the API, regardless of the type of package (either managed or unmanaged).Important After you save a custom setting, you cannot change this value.
8. Protected—If the custom setting is contained in a managed package,subscribing organizations can't see the custom setting: it doesn't display as partof the package list. In addition, subscribing organizations can't access thecustom setting using either Apex or the API, however, developer organizations can.If the custom setting is contained in an unmanaged package, the custom setting isavailable through the Enterprise WSDL like any custom object (as if the Visibility was Public.)
9. Public—The custom setting is available through the Enterprise WSDL likeany custom object. You can package custom settings defined as public. Thesubscribing organizations can edit the values, as well as access them using Apexand the API, regardless of the type of package (either managed or unmanaged).
10. Enter an optional description of the custom setting. A meaningful description will help you remember the differences between your custom settings when you’re viewing them in a list.
11. Click Save.Note Only custom settings definitions are included in packages, not data. If you need to include data, you must populate the custom settings using a standard Apex or API script run by the subscribing organization after they have installed the package.