Custom Metadata Types vs Custom Settings vs Custom Labels 💬 In plain words: Three lookalikes: Custom Metadata = configuration that DEPLOYS with your code (best for app settings). Custom Settings = org/user-specific values, changeable at runtime (hierarchy type is great for bypass switches). Custom Labels = translatable text for the UI. 📌 Example: API endpoint URLs per environment → Custom Metadata (deploys with code, sandbox vs prod values). A 'Bypass_Automation__c' checkbox an admin flips during data load → hierarchy Custom Setting. The word 'Submit' translated to Hindi → Custom Label. 🎬 Real-Life Example: The Fee Table Trapped Inside Code Skyline charges a different delivery fee per city. Apex needs those rates on every booking. The Old/Bad Way: if (city == 'Delhi') fee = 50. Else if (city == 'Mumbai') fee = 65. … Every rate change is a code change, a test run, and a deployment. Why this is bad: Business data is trappe...
In Apex, if you deserialize JSON data into an object, you can access its members using dot notation or square bracket notation, just like accessing any other object's properties. Here's an example of how to do it:
Let's say you have the following JSON data representing an object with members:
String jsonData = '{"name": "John", "age": 30}';
You can deserialize it into an object like this:
// Define a class to represent the structure of the JSON object
public class Person {
public String name;
public Integer age;
}
// Deserialize the JSON into the Person object
Person personObject = (Person)JSON.deserialize(jsonData, Person.class);
Now you can access the members of the `personObject` using dot notation:
String personName = personObject.name; // "John"
Integer personAge = personObject.age; // 30
Or, you can use square bracket notation to access the members:
String personName = (String)personObject.get('name'); // "John"
Integer personAge = (Integer)personObject.get('age'); // 30
Both dot notation and square bracket notation will give you the same result. However, dot notation is more concise and often preferred when you know the specific member names and their data types. Square bracket notation is more useful when you have dynamic member names or when you are iterating over the keys of the object.