Phaniraj Nadiger

🚀 Boosting Efficiency with Apex in Salesforce! 🚀 Here's a look at an Apex class I developed to streamline customer search operations in Salesforce. This class dynamically queries Account records based on PAN Number and Mobile Number, showcasing the power of advanced Apex techniques. Key Highlights: With Sharing: Adheres to the current user's sharing rules and security settings, enhancing data security. @AuraEnabled(cacheable=true): Enables the method for Lightning components and caches results for improved performance. Dynamic SOQL Queries: Constructs queries on-the-fly based on user input, ensuring flexible and accurate data fetching. Conditional Logic: Ensures robust execution by building query conditions only when valid inputs are provided. This is a great example of leveraging advanced Apex features for better performance and user experience in Salesforce! #Salesforce #ApexDevelopment #LightningComponents #DynamicSOQL #DataSecurity #PerformanceOptimization NAZIYA AHEMAD KHATIB Rumana A. Persistent Systems   

163

9 Comments

Apex Sharing: When the Object's OWD has been assigned as "Private". Then, if any of the user Creates a Record inside the object, then Salesforce will make the record to be visible only to the "Record Owner, and His Manager" based on the Role Hierarchy. Other Users inside the Organization, can't access the record. To make the records to be visible to the other users, we are using a "Sharing Mechanism". While Sharing the records to the required User, then Salesforce will store the Sharing Related Data inside the Share Objects. Salesforce provides a separate Share Object for each Standard and Custom Object inside the Organization as below. Object Name Share Object Name ---------------------------------------------- Campaign CampaignShare Lead LeadShare Account AccountShare Contact ContactShare Case CaseShare Opportunity OpportunityShare Hiring_Manager__C Hiring_Manager__Share Position C PositionShare .............. ..............etc. Note: For Master - Detail relation, the child object won't have a shared object. Only for Lookup relationships. Note: Share Objects will be enabled / accessible, when the object's owd is either "Private / Public Read Only". Note: Share Objects will not be available for the Child Object's which are associated with "Master-Detail" association. By using Apex Sharing Mechanism, we can Share the Records to the required users with the required level of access dynamically at runtime, by using Triggers. AccountShare Object: ------------------------ This Object contains all the Account Record's Sharing Related information. It contains the below fields. 1. AccountID: It contains the Account Record Id, which needs to be get Shared to the required users. 2. UserOrGroupId: It contains the "User Id / Public Group ID", to whom the record should be get shared. 3. AccountAccessLevel: Used to specify the Level of Access to be get granted on the Account Record. 1. READ ---> Read Only. 2. EDIT ---> Read and Write Permission. 3. ALL ---> Full Access. 4. OpportunityAccessLevel: Used to specify the Level of Access on the Opportunity Records. Options: 1. READ ---> Read Only. 2. EDIT ---> Read and Write Permission. 3. ALL ---> Full Access. 5. CaseAccessLevel: Used to specify the Level of Access on the Related Case Records. Options: 1. READ ---> Read Only. 2. EDIT ---> Read and Write Permission. 3. ALL ---> Full Access. 6. RowCause: This field is used to specify the sharing reason. Ex: Manual Sharing Rule,...etc. Ex: Account Share accShare= new Account Share(); accShare.AccountId = '0015g000015iLGvAAM'; accShare.UserOrGroupId= 'User Group ID' ; accShare.AccountAccessLevel = 'READ'; accShare.OpportunityAccessLevel = 'READ '; accShare.CaseAccessLevel = 'READ'; accShare.RowCause = 'Manual'; Insert accShare; #SFDX #ApexDevelopment #OOPS #Customization #Configuration #ApexSharing

245

14 Comments

📢 New Blog on SFDC Insights! 🚀 Check out our latest blog by Himanshu Pander ☁️⚡️: "How to Create Your First Apex Class with System Debug". If you're diving into Salesforce development and want to learn how to write Apex classes and debug them in VS Code, this blog is a must-read! 💡 What you’ll learn: 📝 How to write your first Apex class 🖥️ How to use System.debug() for debugging in Apex 🚀 How to execute Apex directly in VS Code and view debug logs 👉 Read the blog here: https://lnkd.in/gcyC4uAD Stay updated with more Salesforce tips by joining our WhatsApp community! 💬 https://lnkd.in/gw-dTKn8 #SFDCInsights #Salesforce #Apex #SalesforceDeveloper #SalesforceBasics #TechTips #CRM #WhatsAppCommunity #Trailblazers

9

We all hv must heard/seen abt impressive earning report by Salesforce for Q3 FY'25. It made their stocks jump upto ~10%. Mark mentioned abt SF turning as Customer 0, Digital labour, Agentic platform,Deals, Results & current/future customers in a call with Jim[Mad money]. Lets check some of the points: ✅ Basics- Q3 earning stats: -Their revenue grew by 8% year over year during the third quarter[ to $9.44B] -Fiscal fourth quarter sales were expected to be between $9.9B and $10.10B; within analysts’ projections of $10.05B. -The company’s net income was $1.5B – a 25% increase from last year’s $1.2B. ✅ SF is Customer 0 -SF has enabled Agentforce for help.salesforce.com -SF has implemented Agentforce on their website for prospects -Hinted towards resource realignment from one role to another due to Agentforce ✅ Hiring -SF executive earlier mentioned abt increased hiring [>1000] to help with the increased demand for Agentforce. -Mark mentioned abt regrp of teams into other roles since Agentic platform is used to aid their end users. ✅ Big deals -More than 200 deals closed in just one week -In Q3, the number of wins greater than $1 million with AI more than tripled year over year and signed more than 2,000 AI deals -Global partners involved in 75% of our Q3 Agentforce deals in nine of our top 10 wins in the quarter ✅ Current/Future customers -Disney, Adecco, Heathrow, SharkNinja -Upcoming*- Benioff Children's Hospitals ✅ Upcoming feature -Agentforce 2.0 - Stay tuned for it ✅ Competitors -He was not so kind on Microsoft & its copilot For a detailed report, please visit the link in comment 1,2 Image, some data points: Thanks Salesforce Ben #marketingchampion #sfmcGuru #sfmc #salesforcemarketingcloud #marketingcloud #marketingautomation #marketingchampions #trailblazercommunity #salesforce #cloud #earning #results #agenticplatfrom #agentforce

28

2 Comments

Salesforce & CPQ facts #15: Redirect to the Quote Line Editor (QLE) from a Custom Action, VF Page, Aura, or LWC: There may be cases where we need to redirect to Quote Line Editor. Then this is the vf page which we need to call. QLE VF page provided by Salesforce CPQ : /apex/sbqq__sb?id={QuoteID} From browser perspective(URL) : http://SalesforceOrgURL/apex/sbqq__sb?id={QuoteID}  #salesforcecpq #salesforce

44

Looking to fetch the report data in Apex ? here is the way.

7

🌟 Salesforce Revenue Cloud vs CPQ 🌟 In the rapidly evolving landscape of Quote-to-Cash solutions, Salesforce CPQ and Revenue Cloud stand out as two powerful tools that cater to diverse business needs. Both products play crucial roles in streamlining pricing and quoting processes, but they offer distinct features and capabilities that set them apart. 🔹 Managed Package vs. Native Platform Salesforce CPQ functions as a managed package, providing exceptional customization and flexibility tailored to specific business requirements. In contrast, Revenue Cloud is built natively on the Einstein 1 Platform, which enhances its scalability and robustness. This native architecture allows for seamless integration within the broader Salesforce ecosystem, making it a compelling choice for businesses looking for a cohesive solution. 🔹 Enhanced Features & Integration Options While CPQ remains a reliable staple for many organizations, Revenue Cloud elevates the experience by leveraging the capabilities of the native platform. This evolution results in richer features, improved automation, and simplified connections with both Salesforce and external systems. As businesses seek to enhance their operational efficiency, these enhancements in Revenue Cloud become increasingly valuable. 🔹 Future-Ready Scalability Revenue Cloud embodies the natural progression of Quote-to-Cash solutions. Its architecture is designed to accommodate the growth of businesses, ensuring that performance remains strong as customer demands and complexities evolve. This future-ready approach positions Revenue Cloud as a leader in meeting the needs of modern enterprises. In conclusion, both Salesforce CPQ and Revenue Cloud offer unique benefits that can empower organizations to navigate the complexities of pricing, quoting, and billing. As businesses look ahead, the emphasis on faster processes, greater scalability, and seamless integration will undoubtedly shape the future of Quote-to-Cash solutions. 🚀 Embracing the Future of Quote-to-Cash The journey towards optimizing revenue processes is an exciting one, and both CPQ and Revenue Cloud are pivotal in driving businesses forward. Whether choosing CPQ or transitioning to Revenue Cloud, the focus remains on delivering exceptional value and enhancing operational efficiency. Revenue Cloud : https://lnkd.in/g2hmgfnN Salesforce Salesforce Revenue Cloud Trailhead #CPQ #QuoteToCash #SalesforceCPQ #BusinessAutomation #SalesforceEcosystem #DigitalTransformation #FutureOfWork

20

Question for Salesforce Developer - I have Class B, and I need the sharing behavior of Class B's methods to be dynamically determined at runtime. Specifically, if Class B is invoked by Class A which is declared as with sharing, then Class B should execute in with sharing mode. However, if Class B is called by a without sharing class, then Class B should execute in without sharing mode. #salesforceinterview#salesforcequestions

115

15 Comments

#TFITips How do you read the URL parameters in Salesforce Lightning Web Component dynamically? How do you use LDS to get the records based on the object dynamically using the same #LWC? #TFI #Techfuge Techfuge India Pvt. Ltd. #lightningwebcomponent #component

4

🔴 🔵How to Authenticate with Salesforce Marketing Cloud API Using AMPscript and SSJS When working with Salesforce Marketing Cloud (SFMC), authentication plays a critical role in accessing and utilizing its REST APIs. These APIs provide a wealth of functionalities, from managing subscribers and sending emails to retrieving data and automating processes. Understanding how authentication impacts these APIs is key to ensuring secure and effective integrations. https://lnkd.in/dgHWbM63 #SFMC #V2Token #AMPScript

49

2 Comments

🛠 CPCP 📦 Salesforce RLM introduces Composable Product Catalog and Pricing, eliminating data duplication for product master data and pricing logic at different customer touch points. Explore the detailed benefits on my blog here : https://lnkd.in/dhEq6M9x #Salesforce #RLM #APIFirst #CPQ

38

Error handling is an important factor to consider while working with Salesforce Flows. In our latest blog, we have discussed the different ways of handling errors in Salesforce Flows. Blog link 👇 https://lnkd.in/dwR8eV6D #Salesforce #Flows #ErrorHandling

17

#Back2Basics In Salesforce, "logic less code" is a design principle aimed at simplifying code by separating business logic from Apex triggers and reducing reliance on custom logic. This approach promotes maintainability, scalability, and testability by encouraging the use of declarative tools like Flows and ensuring the core logic resides in dedicated handler classes. Key Aspects: 1) Trigger Handler Classes: Instead of embedding logic directly in triggers, delegate tasks to handler classes. For instance, a trigger might call AccountTriggerHandler.handleBeforeInsert() to execute the business logic, enhancing reusability. 2) Bulkification of Code: Logic is written to handle multiple records efficiently, preventing governor limit violations. 3) Separation of Concerns: Each class should handle distinct responsibilities (e.g., validation, SOQL queries) to keep the code clean and focused. 4) Testability: Logic in classes can be tested independently of the trigger, improving code reliability and coverage #OpenToWork #LinkedInJobs #Salesforce #SalesforceDeveloper #SalesforceAdmin #Trailblazer #SalesforceCareers #SalesforceLife #SalesforceCRM #SFDC #LWC #LightningWebComponent #Developer #SalesforceNotes #SalesforceTips #SalesforceApex #coding #salesforceConcepts #trailhead

21

3 Comments

📈 Boost your Salesforce development with the Minimal Trigger Framework and best practices! In this video, we walk you through efficient trigger management, using tools like Prettier and Code Analyzer to ensure high code quality. Watch now! 💻✨: https://lnkd.in/g_xzehSq #Salesforce #SalesforceTriggers #SalesforceDevelopment #Winfomi #TriggerBestPractices #Prettier #CodeAnalyzer #salesforcepartner #salesforceimplementation #salesforceaiimplementation #salesforceintegration  

11

Apex Classes are by far the most betrayed entities in Salesforce platform!!! And Apex Test Classes are the most exploited in the Salesforce Development life cycle. How so??? Firstly Test Class are never written the day Apex class is built.... And then on last day of build, the main class is deceived into believing that all it's functionality is working.. but in reality only lines are covered by test class!!! Alas!!! The poor main class only finds it out during UAT about the betrayal .. but, it will already be too late and go-live will be approaching. And once it's live, test class is never looked at to be improved!!! My sympathy to all such betrayed Apex Classes, May they find the right developer to get assertions written atleast as a tech debt!!! PS: Let's get better at test classes by moving away from mindset of just covering lines to writing assertions when ever possible. #salesforce #salesforcedevelopment #salesforcedeveloper #sfdc #justathought #Friday #FunFriday

105

23 Comments

Have you ever thought about having a guru who helps in apex development 🤔 --- 🚀 **Introducing Apex Guru: A Game-Changer for Salesforce Developers** 🚀 In the ever-evolving landscape of Salesforce development, staying ahead of the curve is crucial. That's where Apex Guru comes into play, offering a revolutionary approach to optimizing your Apex code. Now available from the Spring '24 release, Apex Guru is designed to empower developers like never before. 🔍 **What is Apex Guru?** Apex Guru is an AI-driven tool that proactively identifies and resolves performance issues within your Apex code. It's like having a personal assistant who understands your code better than you do, providing actionable insights to enhance efficiency and reliability. 💡 **Key Features:** - **AI-Powered Insights:** Get deep dives into your code's performance without any extra cost. - **Proactive Issue Resolution:** Identify potential bottlenecks and optimize them before they become problems. - **User-Friendly Interface:** Designed to be intuitive, making it easy for developers of all skill levels to navigate and utilize its full potential. 🌟 **Why Choose Apex Guru?** - **Efficiency:** Save time and resources by automatically identifying and resolving issues. - **Performance Optimization:** Boost your application's performance through AI-driven recommendations. - **Cost-Effective:** Access advanced features without additional costs, making it accessible for all developers. 🔗 **Getting Started:** Ready to elevate your Salesforce development game? Apex Guru is now available for Unlimited Edition (UE), Full Copy Sandbox, Signature, and Scale Test customers. Dive in and unlock the full potential of your Apex code today! Follow the Salesforce Ben blog link in comments to learn more about ApexGuru 😃 #Salesforce #ApexGuru #AI #CodeOptimization #Spring2024Release

8

2 Comments

Sandbox Preview and Non-Preview Instance Explained - (Video) https://lnkd.in/d9cK-M8C? To opt out your Org out of Preview, go to this link - https://lnkd.in/d6TgPG4j Salesforce utilizes a structured release cycle with updates three times a year: Spring, Summer, and Winter. To manage these updates, Salesforce offers preview and non-preview sandboxes, providing environments for testing new features and ensuring smooth transitions to new releases. Sandbox Types Preview Sandboxes 1. Purpose: Allow early testing of the upcoming Salesforce release. Administrators and developers can test new features and adjust customizations before the release is applied to production. 2. Timing: Updated to the new release a few weeks before the production upgrade. 3. Selection: Sandboxes are automatically upgraded based on their instance. Administrators can opt in or out of the preview period. Non-Preview Sandboxes: 1. Purpose: Remain on the current release version until the general availability (GA) date of the new release. They provide stability matching the current production version. 2. Timing: Updated to the new release simultaneously with production instances. Managing Sandbox Preview vs. Non-Preview Salesforce administrators can control which sandboxes are included in the preview phase. 1. Opting Out or In: To stay on the current release, refresh sandboxes to non-preview instances before the preview window. To join the preview, refresh sandboxes onto preview instances. To do this, go to this website https://lnkd.in/d6TgPG4j 2. Testing: Use preview sandboxes to test new features, customizations, and integrations to ensure readiness for the new release. Benefits of Using Preview Sandboxes 1. Early Access: Get early access to new features. 2. Preparation: Identify and resolve issues before the production upgrade. 3. Training: Train users on new features pre-release. Example Workflow 1. Check Preview Information: Review Salesforce's documentation on the upcoming release and instances in the preview. 2. Decide on Sandbox Strategy: Determine which sandboxes to keep on the current release and which to upgrade to the preview. 3. Refresh if Needed: Refresh sandboxes to appropriate instances to manage their upgrade status. 4. Test and Prepare: Use preview sandboxes to test changes and document necessary adjustments. 5. Upgrade Monitoring: Monitor the upgrade process to ensure all environments transition smoothly. Strategically using preview and non-preview sandboxes helps organizations minimize disruptions and leverage new features effectively during Salesforce releases. Reference for below screenshot - https://lnkd.in/dqqB7-eS

20

Unleash the Potential of Salesforce Screen Flows to create simple, guided experiences for all users, even without logging in. Improve interaction and success for your business. Blog - https://lnkd.in/dD3m2C2v #SalesforceScreenFlows #UserExperience #NoLoginNeeded #InteractiveWorkflow

8