Jason Lantz

Want to become a Salesforce Agentforce authority? Learn Claude first. Go deep into Claude code, configurations, best practices, etc. Learn what is needed to make Claude work the best for the use cases you have for Salesforce. Then tackle learning Agentforce. The best software practices usually don't come from within the Salesforce industry. It's on us to learn from these industries and then apply these practices to the tool we use the most. Good luck, you've got this! https://lnkd.in/eVJmK6xJ

38

11 Comments

not sure if anyone wants to hear this but Salesforce developers and admin are in for a rough ride. using Claude code and SF CLI can do most of the work. this is not hyperbole

5

What's the hardest part of a Salesforce implementation nobody talks about in the discovery call? 🔹 Data quality 🔹 Stakeholder alignment 🔹 Undocumented legacy logic 🔹 Scope creep after go-live Asking because I see one of these derail almost every project - and it's almost never the one the client flagged upfront. #Salesforce #Trailblazers #SalesforceConsulting

4

Dev team has access to 50,000 employee email addresses. Should they? I recently spoke with a customer. Their Salesforce metadata contains Confidential information. Not just in Production. In EVERY environment: - Dev orgs - Full copy sandboxes  - Partial copy sandboxes What's replicating? - User information (50,000 emails) - Product information - Pricelists The risk is everywhere. Three ways to handle it: Option 1: Redo your architecture Remove sensitive data from metadata (Long-term fix, hard to execute) Option 2: Use Cloud Compliance DataMasker Invokes Apex automatically Wipes metadata clean (100% on-platform solution) Option 3: Write custom Apex Build your own solution (Most companies don't have time) Here's what concerns me: This metadata risk exists In most organizations. They just don't know it yet. Have you seen these use cases? How do you protect YOUR metadata From leaking confidential information? PS: Doug Merrett and I are hosting a webinar on Salesforce Security & Compliance for Financial Services.  Link in the comments, please join us and 135+ others. #Salesforce #DataSecurity #MetadataManagement #EnterpriseArchitecture

12

6 Comments

When we launched the Salesforce Lightning Design System nearly ten years ago, it was about more than components and tokens — it was about creating a shared language for how we and our ecosystem design and build at and on the Salesforce platform. Today, with SLDS 2 going GA, I can’t help but take a moment to reflect. This milestone is more than a product release; it’s the result of years of listening, learning, and co-creating with an extraordinary community of customers, partners, and colleagues. SLDS 2 is not just a new system — it’s a foundation built for what’s next: AI-driven experiences, enterprise scale, and agentic design patterns that adapt and respond to people, not pages. To my entire dedicated team and everyone who has contributed, challenged us, and believed in what design systems can unlock — thank you. You’ve made this system stronger, smarter, and more human. A design system is never just a set of components. It’s the patterns, guidelines, visual language, tooling, and design experts who have a passion for systems design that inspire makers to innovate and craft exceptional experiences — all supported by a flexible framework that empowers you to make it your own. We’re launching a new customer story alongside SLDS 2 featuring Stephy Hogan and Cassandra Soryung Yu because, ultimately, this isn’t about what we built. It’s about what you will create with it. The real measure of a design system is in the products, stories, and impact it enables — and those belong to you. Here’s to the next chapter of design at Salesforce — and to designing systems that keep evolving right alongside us. Salesforce Designers #designsystems #slds #ux #enterprisedesign

200

9 Comments