Daily Learnings: Mon, Jan 22, 2024
‘As I am, so are they; as they are, so am I.’ Comparing others with oneself, do not kill nor cause others to kill. — The Buddha
Notes on Trailhead Maintenance
Notes from things learned while I was completing my trailhead maintenance for all of my Salesforce credentials
- You can now enable Person Accounts in SFDC without contacting Support, as long as the following is true in your org
- Account object has >= 1 record type
- User profiles that have read permissions on Accounts also have read permission on Contacts
- OWD sharing settings or Contact is Controlled by Parent, or both Account/Contact are Private
- Event-Driven Architecture Updates
- You can filter which events are delivered based on the Filter Expression that is part of the
PlatformEventChannelMember- Works for Change Data Capture events as well as Platform Events
- I think this works for CometD and Pub/Sub APIs
- Works for Change Data Capture events as well as Platform Events
- On CometD subscriptions only, you can also group platform events to push multiple types of events to a single stream / client subscription instead of 1 subscription per event
- You can filter which events are delivered based on the Filter Expression that is part of the
- Apex Code Coverage Updates
- For all 2GP and unlocked packages, you can run a report using the
sfdxCLI that will show all Apex classes that are low on code coverage
- For all 2GP and unlocked packages, you can run a report using the
- Updated Salesforce OAuth Flow: Client Credentials Flow
- New OAuth flow for server-to-server communication that is a more secure alternative to the Username/Password flow
- Documentation
- Does not support refresh tokens
- A much easier-to-implement (also less secure) alternative to the SFDC JWT Bearer Token Flow