2 - SOQL : Parent to Child Relationship Queries

SOQL : Parent to Child Relationship Queries


FOR STANDARD OBJECTS==>. **For Relationship Queries we need ---> Child Relationship Names which is found in the ---> Child ---> Field & Relationships ----> in Lookup (Datatype) --> click it --You get Child Relationship Names

// Get all related contacts of an account

SELECT Name, Phone, Website, (SELECT Name, Department, Email FROM Contacts) FROM Account


FOR CUSTOM OBJECTS==>. **For Relationship Queries we need ---> Child Relationship Names which is found in the ---> Child ---> Field & Relationships ----> in Lookup (Datatype) --> click it --You get Child Relationship Names + (YOU ADD suffix __r in the  FOR CUSTOM OBJECTS==>. **For Relationship Queries we need ---> )

// Get all books(child object) of an author (parent object)

SELECT Name, (SELECT Name FROM Books__r) FROM Author__c

RESULT CAN HAVE MULTIPLE CHILD RECORDS

Limitations 

Only one level child can be queried

20 childs maximum can be queried


SOQL : Child to Parent Relationship Queries


FOR STANDARD OBJECTS==>. **For Relationship Queries we need --->Field Name which is found in the ---> Child ---> Field & Relationships ----> in Lookup (Datatype) --> click it --You get Field Name

// Get account information from contact

SELECT Name, Phone, Department, Account.Name, Account.Website FROM Contact


// get grandparent (user) object details

SELECT Name, Phone, Department, Account.Name, Account.Website, Account.Owner.Name FROM Contact

// Get author(parent object) from books(child object)

SELECT Name, Price__c, Author__r.Name FROM Book__c

ONLY ONE PARENT RECORD


Limitations 

Only FIVE level parents can be queried

55 parents maximum can be queried 


Data in Apex from SOQL


// Retrieve all books and assign to a List collection

List<Book__c> books = [SELECT Name, Price__c FROM Book__c];

for(Book__c book : books){

    System.debug('Book Name: '+book.Name+' Book Price: '+book.Price__c);

}



APEX (Binding) Variables in SOQL using COLON(:)


List<String> accountNames = new List<String>();

accountNames.add('Sample1');

accountNames.add('S2');

List<Account> accounts = [SELECT Id, Name, Phone, Rating FROM Account

                          WHERE Name IN :accountNames];


DYNAMIC QUERIES


String accountClass = 'B';


String queryString = 'SELECT Id, Name, Phone, Rating FROM Account';


if(accountClass == 'A'){

    queryString += ' WHERE Rating=\'H\' AND Type=\'Prospect\'';

} else if(accountClass == 'B'){

    queryString += ' WHERE Rating=\'AA\' AND Type=\'Other\'';

} else {

    queryString += ' WHERE Rating=\'BB\'';

}


List<Account> accounts = Database.query(queryString);

System.debug('Accounts '+accounts);



 sObjects (Salesforce Objects) 

In Salesforce, sObjects (Salesforce Objects) are foundational to handling data within Apex (Salesforce’s proprietary programming language). They are used for various reasons:

1. Universal Representation of Salesforce Data

  • sObjects represent records of Salesforce database tables (standard or custom objects) within Apex, allowing developers to interact programmatically with Salesforce data. Each Salesforce object, like Account, Contact, and Opportunity, is an sObject type, making it easy to work with both standard and custom object data in Apex.

 







Comments

Post a Comment

Popular posts from this blog

API Names in Salesforce

 In Salesforce, an API Name is a unique identifier for metadata components like fields, objects, or custom settings that enables external systems, scripts, and integrations to reference Salesforce data programmatically. The API name remains consistent, even if the label displayed in the user interface changes, making it essential for maintaining integration stability. Key Characteristics of API Names Field and Object API Names : Standard object and field API names generally mirror their label names, but with spaces removed. Custom fields and objects have the suffix __c , denoting them as custom. Example: A custom object called "Project" would have an API name of Project__c . A custom field called "Start Date" on the Project object would have an API name of Start_Date__c . Case-Sensitivity : API names in Salesforce are case-sensitive , so it’s essential to match them exactly when using them in code or integrations. Usage : API names are used in SOQL queries, Apex co...
Read more

18 - LWC - BEST PRACTICES - For accessing HTML elements and their values in JavaScript

 In Lightning Web Components (LWC) , best practices for accessing HTML elements and their values in JavaScript involve using template.querySelector , template.querySelectorAll , and data-* attributes. Here’s a guide to help you follow these best practices effectively: 1. Use template.querySelector and template.querySelectorAll Since IDs can be unpredictable in LWC , the template.querySelector method is generally preferred. You can use CSS selectors , including class names, tag names, and data-* attributes, to locate elements. html Copy code <!-- template.html --> < lightning-input class = "my-input" data-id = "specialInput" value = "Sample Value" > </ lightning-input > javascript Copy code // component.js // Accessing the element const inputElement = this . template . querySelector ( '.my-input' ); // Getting the value const inputValue = inputElement. value ; 2. Use data-* Attributes for Specific Identifiers For ele...
Read more

6 - Object Relationships (Lookup and Master-Detail and Junction Objects)

 Here's a tabular comparison of the Lookup and Master-Detail relationship types in Salesforce: Feature Lookup Relationship Master-Detail Relationship Definition and Usage Loosely coupled; records are linked but can exist independently Tightly coupled; child record depends on the parent for existence Data Integrity and Ownership Child record does not inherit parent’s sharing or ownership Child inherits sharing, permissions, and ownership from the parent Roll-up Summary Fields Not available Available; aggregates values from child to parent Required Field Optional; child can exist without a parent Required; child must have a parent Cascade Delete Optional (not automatic) Automatic; deleting parent deletes all related child records Security and Access Child has independent sharing settings Child inherits sharing settings from the parent Hierarchy Depth Flexible; supports multi-level relationships Limited to strict parent-child hierarchy with up to two relationships This structure pro...
Read more