Samsung’s announcement of the new $450 Galaxy A37 and $550 Galaxy A57 today brings good news and bad news for value-conscious customers looking for a cheaper phone.
Much like we’ve seen on the flagship-level Galaxy S26, both phones are priced higher than the A36 and A56 they are replacing — in this case by $50 — though storage options for both phones still start at 128GB. However, both phones did get a design improvement that features IP68 water resistance and will feature the newly updated Circle to Search, with enhancements like Find the Look for identifying outfits.
Starting with the $450 Galaxy A37, this phone has a 6.7-inch display with a 120Hz refresh rate. It runs on Samsung’s Exynos 1480 processor and has a 45-watt wired charging speed, which Samsung says will recharge its 5,000-mAh battery from 0% to 65% in 30 minutes.
The lavender edition of the Galaxy A37 is easily my favorite color of the bunch.
Mike Sorrentino/CNET
The phone is made from plastic and comes in four colors: charcoal, gray-green, white and — my favorite — lavender. (Note: Samsung adds the word “Awesome” in front of all of these color names, but I’m going to save us from this.) The A37 also comes in a 256GB model that costs $540.
The A37’s cameras include a 50-megapixel wide, an 8-megapixel ultrawide and a 5-megapixel macro on the back, along with a 12-megapixel selfie camera on the front. The A37 gets a sampling of Galaxy AI features, including object eraser for editing photos, language translation and an upgraded Bixby assistant.
The Samsung Galaxy A57 includes the Best Face feature for fixing photos where someone is blinking.
Mike Sorrentino/CNET
The $550 Galaxy A57 moves up from plastic to a metal body but only comes in navy. It also has a 6.7-inch display, but weighs in at 179 grams, which is markedly lighter than the A56’s 198g. During my hands-on time, it was noticeably light, especially for a phone with the larger display size.
The phone runs on Samsung’s Exynos 1680 processor. It also gets a few more AI photo editing tools like Best Face for fixing group photos where someone is blinking.
The cameras on the A57 include a 50-megapixel wide, a 12-megapixel ultrawide, and a 5-megapixel macro on the back and, like the A37, includes a 12-megapixel selfie camera. A step-up 256GB model costs $610, but it’s worth noting that this price is really close to the $650 Galaxy S25 FE, which includes all of the Galaxy AI features along with a telephoto camera.
I’m bummed but not surprised to see the increased cost of the A37 and A57 versus last year’s models, which a Samsung representative said is attributable to current market conditions when I asked about the ongoing RAM shortage.
During my hands-on time, though, I did find both phones to look quite nice, with the lavender model likely providing plenty of competition to the $499 Google Pixel 10A’s colors. Both phones will go on sale on April 9.
Custom settings are objects that developers use to create different customized sets of data that have an association with the company, user, or profile. There are options where you can set the custom settings to either public or private. Some of the areas where custom settings get applied are the fields, Apex, flows, SOAP API, and validation rules. The data created by customer meetings must meet the user’s needs, allowing users to access it faster using the application cache.
When you have data using the settings, users do not need to use database querying languages or the Salesforce Object Query Language to get the data. It uses custom objects which developers build to fix all the business processes and information that does not work well with the Salesforce objects. Many businesses should learn how to use custom settings and benefit from them. Some of the custom fields that the developers use are currency, checkbox, phone number, date and time, URL, text, number, textarea, percent, e.t.c.
The settings can lack some fields like lookups, formulas, picklists, e.t.c. which are important to use. It also lacks page layouts that developers can use. The lack of layouts forces developers to use visual force pages to meet the requirements. When working with these settings, there are no rules that one must use.
It works with how the custom objects function. The main purpose of this custom setting is to cache all the data. It reduces the cost of the data due to easy access to the data. It makes the accessing of static data across the company easy. It eliminates the use of SOQL queries which are sometimes against the limits. What the users need to do is put the data in this type of setting without writing any SOQL for accessing the data. The data provided in the list settings does not vary according to the users or profiles, making it impossible for anyone in the company to access it.
The data is useful to different departments of the company. It enables the developers to have reusable data which everyone can access in the company. This setting is good for the type of data sets that companies use mostly in their salesforce applications.
We create a list custom settings by following the steps below:
Locate the menu and search for the Schema settings, toggle the button of Manage list custom settings to turn it on. By default, most of the settings are in hierarchy custom.
Under the Custom Setting Definition, input the names under the label and Object Name and then change the Setting type from Hierarchy to List.
When working with data like phone numbers, when you input the country codes into the labels, It automatically fetches into the form without querying the database. After filling in the details under the label and other fields, click on the Save button.
Navigate to the custom fields, click on the New button, and it will open a new page where you get prompted to choose the Data type and choose the type according to the data you entered in the custom definition. If it was phone numbers, choose the phone and click Next. We will select text.
On this page, there are several fields like Field label, length, field name, Description, e.t.c. Fill them out and click Save.
Under the created label, click on the Manage option to provide new fields.
After all, the new fields click Save, and you can view your complete list of custom settings.
Salesforce Training
Master Your Craft
Lifetime LMS & Faculty Access
24/7 online expert support
Real-world & Project Based Learning
Hierarchy Custom Settings
Hierarchy custom settings help in ensuring the majority have the advantages for users. Its logic is efficient and enables users to customize their settings using different settings and rows. The settings match particular profiles and contacts that will meet the requirements of the company’s clients. This type of setting can scan all the client companies and their necessary profiles, look at the tasks handled by different people, and ensure that the final values shown to the user are more accurate and specific to what they want.
It makes the companies make certain settings to several profile settings meant for the users, which get subjected to the user settings individually. They help the companies and their clients to define all their data hierarchically. This type of setting is suitable when defining defaults used by specific Salesforce applications, relying on the users, companies’ needs, and certain profiles. Hierarchy custom settings sync well with the Salesforce functionalities since they are highly customizable, and you can change them to meet the customer’s needs.
We can create an example of a Hierarchy Custom Setting using the steps below:
Navigate to the Custom Settings option, input the data under the Label, Object Name, Setting Type by default is a hierarchy and click on the Save button.
A new dialog box will open, and you will get prompted to choose the type of data type, select the one that matches your inputs, and Save.
Under the next step, fill in your Field Label, Length, Field Name, and Description, among others, and click on the Save option.
When the dialog opens, click on the New button to create organizational access to the data.
After saving, you will get options to add other alternatives.
Another dialog box will pop up, prompting the administrator to add the profiles that will get associated with the values. When you click the Save button, several users will be under the custom settings. And that’s the whole process of creating the hierarchy of custom settings.
How to Create Custom Settings
Log in to your Salesforce CRM, locate the Custom Settings, and several fields require one to fill. Under the label and Object name, input worker for both fields. Under the Settings section, choose between list and Hierarchy. Under Visibility, set it to public, enter the Description, then click on the Save button.
In some cases, you find that some parts of the settings section got disabled, you need to navigate to the schema settings and change the settings to enable it. Go to the custom fields and create the field by entering data into Field Label, Data type, API name, and action. To add data, hover over the Action settings to add more data.
Subscribe to our YouTube channel to get new updates..!
Why do we need Custom Settings?
Using custom settings in the Salesforce CRM and applications has several benefits. This include :
It allows faster fetching of data, for example, if you have many records and you want to retrieve one row, you will use custom settings to get the result in a short period due to the ability of customer settings to get stored in the cache.
They also avoid the chances of hitting the governing limits. There are several governing limits from SQL queries, DML statements, Sendmail methods, SOSL queries, e.t.c.
Due to the use of application cache, one can have faster data access, leading to better performance.
It enables the users to access different data according to the user’s profile and role in the organization, which promotes data integrity.
If you lack knowledge about databases or the Salesforce Object Query Language, it helps you avoid learning them.
There are several ways of fetching custom settings in Salesforce. These methods are:
To fetch custom settings, it depends on the type of custom settings. Let us look at all types of settings.
How to fetch data on list custom settings.
We use the getAll() method to fetch certain custom fields found in List settings. The method returns a list of the names and all the setting records i.e
Map var =
CustomApiName.getAll();
Eg: Map worker = Worker__c.getAll();
We use the getValues() method to fetch the values that match with a certain dataset. It normally works for both the custom settings i.e
CustomApiName var = CustomApiName.getValues(name of dataset);
For example Worker__c stud = Worker__c.getValues('Mark');
To fetch values for hierarchy custom settings, we use the methods below to achieve the same:
We use getOrgDefaults() method to return the data set records for the company i.e
CustomApiName var = CustomApiName.getOrgDefaults();
We use getInstance(input the user id or the profile id) method to get data records for a certain user or profile details i.e
CustomApiName var = CustomApiName.getInstance(userId/ProfileId);
We use the getInstance() method to get the records for the logged users.
CustomApiName var = CustomApiName.getInstance();
Limitations of Custom Settings in Salesforce?
Some of the limitations of using Salesforce include:
Each custom setting can only handle 300 fields. If there are more than 300, they can’t support more than 300 fields.
When storing the cached data, the storage will depend on the licenses. For 1 MB, you get the multiplication by using the licenses each organization owns. For example, a company can support up to 4MB of storage if it uses four licenses.
When you want to access an undeleted custom setting, you will get an error if you don’t have permission to access the custom settings.
There is no option to share the custom setting records and objects.
When creating the custom setting, you cannot get the ownership after its creation.
When dealing with each certified package, one gets a separate limit when working with the company limit.
Conclusion When creating custom settings in a distributed package, you must develop several builds for populating the custom settings with data after the package installation. Implementing custom settings is easier and straightforward and has many benefits for the users. The article has enabled you to better understand the two types of custom settings, the advantages, and how to install them in your application.
To provide the best experiences, we use technologies like cookies to store and/or access device information. Consenting to these technologies will allow us to process data such as browsing behavior or unique IDs on this site. Not consenting or withdrawing consent, may adversely affect certain features and functions.
Functional
Always active
The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
The technical storage or access that is used exclusively for statistical purposes.The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.
