#Salesforce_developer4 utenti parlano di questo argomento

🎉 Just Hit Double Star Ranger! 🌟🌟

Thrilled to share that I have officially unlocked the Double Star Ranger rank! 🚀 It has been an incredible journey deep-diving into the platform, sharpening my Salesforce development skills, and tackling new challenges badge by badge.

A huge thank you to the amazing Trailblazer community for the constant inspiration, resources, and support along the way. 💙

Next stop: Triple Star Ranger! 🏔️✨

#Trailhead #Double Star Ranger

By the way, does anyone know if there are currently any official Trailhead swag kits or vouchers available for reaching this milestone? Would love to proudly wear some Ranger gear! 

#Salesforce Developer #Salesforce Admin #Salesforcearchitects #Salesforceadmins #Salesforce_developer #Salesforce #SalesforceArchitect

Know your org better than the admin who left — OrgSage beta is live

Hey everyone,

How many times have you inherited a Salesforce org and had no idea why things were built the way they were? Or hesitated to delete a field because you weren't sure what would break?

We built OrgSage to answer one question: "What happens if I change this?"

OrgSage connects to your Sandbox or Developer Edition org (quick package install + OAuth — metadata only, never your data) and maps every dependency — fields, flows, triggers, validation rules, permissions — so you can understand what you're working with before you touch anything.

A few things it can do:

→ Ask in plain English: "What breaks if I delete Account.Customer_Tier__c?" and get a full impact analysis — which automations, page layouts, and apex classes reference it

→ Cross-org impact analysis: Connect multiple DEV orgs and see how a change in your workstream impacts another team's org — no more surprise conflicts when workstreams merge

→ Detect automation conflicts — when a Flow and an Apex Trigger both write to the same field, see the execution order and which value actually persists

→ Compare orgs — see exactly what differs between DEV, QA, and Production with severity ratings on every change

→ Map relationships and references better than Schema Builder or "Where is this used?"

Try it at getorgsage.com — just connect a sandbox and start exploring.

We're looking for developers and architects willing to try it and share honest feedback — what's useful, what's broken, and what's missing.

🚀 Code With Sally · Mastering Claude Code · Part 4 is happening live Tuesday, May 19! 

🗓️ Tuesday, May 19 · 12:00–1:30 PM ET 

🔗 Zoom:

Joining us again: Bill Kuehler — Salesforce MVP, Golden Hoodie Recipient — for Part 4 of our Mastering Claude Code series. 

Claude can sometimes get it wrong — over-complicating things or missing the mark entirely. This time, we're not just building. We're pushing back, redirecting Claude to something simpler, and testing what we ship before we call it done. 

What we'll cover: 

✅ Pushing back when Claude over-complicates 

✅ Refactoring the Apex from Part 3 to something cleaner 

✅ Finishing the Detailed Notes LWC (save, edit, delete, split-panel UI) 

✅ Deploying the component to Salesforce 

✅ Running real browser tests with Playwright CLI 

✅ Live community Q&A 

Drop in live and bring the questions with you 🙌 

New to the series? Catch up on Parts 1–3 first on the Code With Sally YouTube channel 

Excited to invite everyone to an upcoming Code With Sally session featuring Jeff Douglas, Product Management Director, Agentforce Vibes @ Salesforce. 

🗣️ The Complete Rundown: What Shipped for Agentforce Vibes at TDX 

📅 Thursday, April 23 at 12 PM EDT 

📍 Zoom Link:

🔗 Linkedin Event:

This will be a right-after-TDX breakdown of what shipped for Agentforce Vibes, what’s new, why it matters, and what teams building on Salesforce should expect.  

We’ll also talk through how capabilities like Abilities, Skills, deeper context, and multimodal inputs are starting to come together into a more complete development flow. 

A huge thank you to Jeff for joining us for this session. Really excited for this conversation.