13 - Triggers BEST PRACTICES

 1) Dont write all code in Triggers but shift it in APEX Classes

Comments

Post a Comment

Popular posts from this blog

17 - LWC - Project structure / Javascript / Databinding / CSS

Image
 Javascript knowledge : Github-JS DirectFile ONLY MANDATORY FILES XXX.js-meta.xml XXX.js ------------------- LWC Databinding HTML To JS --> Eventhandler (onchange) JS To HTML --> @track HTML ---> <div>Hello {myGreeting}</div>  JS ---> @track myGreeting = 'World'; CSS .greeting-class{     color: Red; } div{     border : 5px solid blue; } :host{     border : 7px solid red; } <div class="greeting-class"> <div style="color: red; background:black;">
Read more

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