Welcome to SFDCFacts - Your Ultimate Salesforce and Technology Learning Hub!
At SFDCFacts, we provide expert tutorials for Salesforce professionals, developers, and admins. From Apex and Lightning Web Components (LWC) to Flow automation, we cover everything you need to succeed in the Salesforce ecosystem. Beyond Salesforce, we also explore modern web technologies and cloud computing, giving you a well-rounded tech learning experience.
✨ What you'll find: - Salesforce development, admin tips, and certifications - Apex, Visualforce, LWC, and Flow tutorials - Integration and automation best practices - Web and cloud technologies
Check out my Hindi RU-vid channel for industry insights and tech discussions: www.youtube.com/@lifeofmanish
🌐 Visit: SFDCFacts.com 🎓 Courses: - Apex Development : bit.ly/sfdc-dev-promo - LWC Development : bit.ly/lwc-promo
I like this raw video ....especially where you got stuck at WhoId and WhatId on lead ...this shows that even experienced folks can get stuck on simple things despite having lot of experience ...so it is ok for us newbie to fail and learn from it. We don't have to know everything.
I started learning my saleforce journey from your SFDCFacts channel, right now i am learning salesforce development and this video is super useful. you are my inspiration. great comeback sir!
Hi Manish, could you please explain the impact on heap storage when instantiating new case inside for loop in Helper class i.e. parentCaseToUpdate.add( new Case ()).. I basically store the result of aggregate query in Map<id,Decimal> and then update the parent cases by iterating once again using for loop. Which approach is better? I will amend my logic accordingly. Thank you.
Don’t think there would be any heap impact as you are using the heap to store parent cases any way in both approaches, however, there is some unnecessary processing (so slight impact on CPU) if you first store query result in a map and then iterate over the map. You can just directly use soql for loop and build your parent cases to update
The last problem statement was awesome! Well with clean code, step by step build up. It covers all fundamentals and corner cases. Such triggers where update on child should update on Parent is sort of a template to mug up😆
I have the entire course on Salesforce development that covers asynchronous apex as well very extensively. But I will add this to my list of crash courses to create a crash course on Async Apex
Whether you're gearing up for an interview, transitioning from Salesforce Admin to Developer, or just starting your Salesforce journey, this crash course is tailored for you. Let me know what topic you want me to cover next. For Complete Apex Development tutorials, enrol in my Udemy course: www.udemy.com/course/salesforce-development/?referralCode=C44BBFDBBBA789BC6A3D
