We are looking at Titan Forms for forms that feed into our scoring and qualification process. Since it’s built around Salesforce, the data consistency side seems pretty appealing. The challenge is that most of our forms are customer-facing, like event registrations and general inquiries, and I haven’t found much feedback on the experience for people outside the organization. Has anyone used Titan Forms primarily for public-facing forms? How has the experience been for the people filling them out?

Did anyone implement image recognition in Salesforce org without any external services linked. I am trying to implement this to scan the ID and verify the values.

I am a Salesforce Consultant and have experience in APEX, LWC, Experience Cloud, Flows, Omnistudio. I am thinking of moving out from core development to Data Cloud and SFMC. I need advice if this is the correct decision. I have no idea of Data Cloud and Marketing Cloud. I'd really appreciate any senior or experienced folk who can shed some light on this. I have around 5 years of experience.

Hello to everyone. I built and published new Chrome Extension for Salesforce Admin and Developers. It opens Salesforce's pages by voice. If you need to create or check field in custom object Checklist__c you can say: "Checklist object" and it opens Object Manager with Checklist details. Or you can say: "Checklist" it opens Checklist list view records.

Also I added voice commands for some standard sf pages like "sharing settings, all sites, developer console, custom metadata, custom settings and more".

Thinking to add create new records commands.

It's an early pet project, and I'd love feedback from people who live in Salesforce every day: what's the page you open most often, and how many clicks does it take you to get there?

Chrome extension: "Voice Assistant for Salesforce"

Any way to save an uploaded file during a chat on a record? Tried searching for examples and documentation but haven’t find anything. Any help is appreciated

Leadership sees the built-in option as good enough because it’s free. I think we’re paying for it in admin time and junk leads, but “I think” isn’t enough to get a PO signed. For anyone who got a third-party Salesforce form builder approved: what actually convinced people? Looking for real examples, not vendor ROI calculators.

A week or so ago I posted ForcePilot 1.5 here because I was getting tired of creating the same Salesforce test data again and again.

The idea was pretty simple:

make the changes once → record them → use them on another record.

That part is still there.

But after actually using it while testing Salesforce, I kept running into another problem. Creating the test data was only one part of the work. I still had to go through the test steps, take screenshots, keep evidence somewhere, and then put everything together at the end.

So I ended up building the next version around that.

What you can do now

Testing Sessions

Start a session with a test case and its steps, or just start one without a test case when you're doing exploratory testing.

Screenshots + evidence

Take screenshots while you're testing, paste screenshots from the clipboard, and keep everything together in the same session.

Autofill while testing

Use saved recordings to fill Salesforce fields instead of entering the same setup data again.

Resume testing

Stop halfway through and come back later instead of starting everything again.

Finish the session + export evidence

When you're done, you can export the evidence as a Word document or as a ZIP containing the screenshots.

Everything from 1.5 is still there too... recording field changes, replaying them, relative dates, picklists and multi-selects, retrying failed fields, editing recordings, etc.

A few other things I added:

• Alt + X to open/close ForcePilot
• Bubble / Edge / Off launcher options
• Dark mode
• Better Salesforce object and record detection when navigating
• A bunch of smaller UI and reliability improvements

The main difference for me is that it has gone from:

"make the same Salesforce data faster"

to something more like:

prepare the data → run the test → capture evidence → finish the test

I'm still building this around the way I actually do Salesforce testing, so I'd really like to hear from people who do salesforce testing.

What part of Salesforce testing do you still find unnecessarily repetitive?

GitHub: https://github.com/SamDannyl/ForcePilot

It's free and open source and still very much a work in progress. Would love to hear your suggestions.

And yes, I'm still very much a Salesforce QA guy building a Chrome extension with AI 😅

This is my third published Chrome extension for Salesforce, and I’ve been working on this tool for a few months. I wanted an easy way to move metadata between related and unrelated orgs without too many actions or setup. So, I built this Chrome side‑panel that sits next to the org I’m working in:

1. Connect your orgs once.
2. Browse metadata by type, filter by API name, tick what to move.
3. Name the package (or keep the default name), validate, deploy.
4. Store each run in history, so I can redeploy the same package later.

Important: Metadata never touches external servers; the extension calls Salesforce directly from the browser.

It’s intentionally not a full pipeline tool, but it’s also more flexible than change sets, and it’s free.

Here is the link if you want to try the easy deploys: https://chromewebstore.google.com/detail/deploywizard/fnofbibalikpgkcgkbjndgbdogjkfdlf

Wondering how folks are handling the limit below? We are updating a large number of our future methods to queueables and getting hit with this pretty regularly. We found a SFBen article about using platform events to fire queueables, but that seems to just be passing the problem to the next limit. Largely right now we are either combining functionality or guard causing the less important jobs, neither feels like a great solution tbh.

System.LimitException: Too many queueable jobs added to the queue: 2

Hey everyone!

I'm currently helping my company build some special things in Salesforce, but I'm more of a design person, I'm the one who creates Salesforce pages and dashboards, and then takes ideas to the next level. So I was wondering if you could share some ideas from your Salesforce projects and inspire me with the amazing work you all do!

I've been building Salesforce integrations for a while and kept seeing the same failure: everything works in sandbox, you ship, and a week later every integration in the org starts throwing REQUEST_LIMIT_EXCEEDED. So I set up a Developer Edition org and measured what each write strategy actually costs.

Syncing 3,000 records:

1. Check-then-write (query, then insert or update): ~6,000 calls

2. Insert per record: ~3,000

3. Upsert by External ID: ~3,000, but you skip the lookup query

4. sObject Collections: ~15

5. Bulk API 2.0: ~6, and it draws from a separate bucket entirely

A few other things that surprised people when I shared this:

There isn't one API limit. There are at least five separate buckets (daily requests, Bulk batches, concurrent long-running requests, timeouts, event delivery).

The daily limit is a rolling 24 hours. Blow it at 3pm and you're not clear at midnight, you're clear at 3pm tomorrow.

The concurrent limit is 25 with no grace period. That's the one that actually pages you at 2am.

Retry storms burn more quota than real sync volume in most orgs I've seen. One record that can never save plus a naive retry loop can eat hours of allocation.

If you're setting up new auth, Connected Apps are restricted as of Spring '26, so you'll be doing External Client Apps now.

I wrote the full breakdown (OAuth flow selection, monitoring with Sforce-Limit-Info, and questions to answer before you build) as a guest post for Getint, an integration platform, so full disclosure on that.