I guess with sharing and without sharing only see record level things not object and field level security That is handled with security enforced and fls Let me know if I am wrong
This is the best Salesforce content I've seen on RU-vid and I've watched a lot. I just want to say thank you for this. The blog is also very well written and straight to the point. Great job!
I am waiting for LWC series since long time. I have watched complete series of Developer Interview Questions and Answers. It was awesome. I really appreciate it. It would be great help if you release LWC series asap. Thank you..!!
Ashfaq - Your videos are really informative. Thanks Just one question - the example you used while explaining SLA holds good to be a B2C than B2B. Have worked on both these models till date and most of the times have used SLAs for B2C - have very bad experience of my organization paying penalty for not meeting it 🙂
By default, when you delete an account in Salesforce, all related contacts associated with that account are also deleted unless you have specific configurations in place to prevent it. This behavior is due to the relationship between accounts and contacts: Parent-Child Relationship: Accounts and contacts have a parent-child relationship, where the account is the parent and the contact is the child. Cascade Delete: When the parent record (account) is deleted, the child records (contacts) associated with it are also deleted by default as part of a cascade delete. This is a built-in Salesforce functionality designed to maintain data consistency and avoid orphaned child records.
