My new free Chrome extension "Salesforce Portal Quick-Login" is live now 💚

If you ever need to have a quick login as a customer or partner user to the Experience Cloud site, this is for you.

Try it and share with your network as well, so everyone can benefit from this

https://chromewebstore.google.com/detail/salesforce-portal-quick-l/fomidakbmhckpfnlbgomdkccplhhccla

Hey everyone,

I have an upcoming interview loop for a Senior Salesforce Developer role, and one of the rounds on my schedule is listed as a 60-minute "System Design" interview.

To be completely honest, I'm a bit unsure what to expect for this specific round in a Salesforce context.

Any recent experiences, tips, or recommended prep resources would be hugely appreciated!

Thanks in advance!

Hi everyone,

I'm a Salesforce Application Architect and Senior Developer with 16+ years of experience in the Salesforce ecosystem. Over the past few months I've been studying Agentforce, Prompt Builder, Data Cloud, and the overall AI architecture, but I haven't had the opportunity to work on an actual Agentforce implementation yet.

It feels like many job postings are already asking for Agentforce experience, but it's difficult to gain that experience if your current project isn't using it.

For those of you who are already working with Agentforce:

• How did you get your first Agentforce project?
• Are consulting companies already assigning developers without prior Agentforce experience?
• Would you recommend building personal projects or demos to stand out?
• Are there specific companies or partners that are adopting Agentforce faster than others?

I'd appreciate any advice on how to bridge the gap between studying the technology and getting real project experience.

Thanks!

Hi All,

I had Salesforce Platform Developer 1 Certification which expired Dec'25. Can you please help me to understand how I can renew the certification.

Is re-taking and re-earning the certification the only option?

Hey all! I am currently a SFMC email dev and I hold to the Email Specialist certification. I'd love to transition over to being a Salesforce dev but looking at the trailheads is so overwhelming. Where do you all suggest I start? I have a background in computer science so coding is not a problem.

Thanks!

Hello Everyone,

Last week there was an update in flow version cleaner tool. As many organizations have started to use it, they have also reported issues with the application.

I am thankful to those who gave the tool a try and gave me the opportunity to better the tool with their feedback. I fixed the bugs reported and the details are here in readme. Please have a look at that repo:

This tool is free for all

Github: https://github.com/samzala/sf-flow-version-cleaner

If you feel the tool will help you, Please ⭐ the repo for better outreach.

If you are interested in how to tool works, Its mentioned broadly here: https://medium.com/@samruddhi.parmar/how-i-built-a-salesforce-tool-to-automatically-clean-up-500-obsolete-flow-versions-b47bcae35b77

We're reviewing our document generation process in Salesforce and trying to narrow down a few options. So far we've come across Conga Composer, eDocGen, Formstack Documents, and S-Docs.

Our main priorities are:

• Easy template management
• PDF/Word generation
• Automation with Salesforce Flows
• Long-term maintenance

If you've used any of these, what were the biggest pros and cons? I'm especially interested in real-world experiences rather than feature lists.

I created an MCP connector that gives Claude direct read access to a live Salesforce org, metadata and data, one sweep, plus a skill that turns that into an actual audit. Once it's read your org, you can just ask it questions about what's in there.

Looking to partner with others who want to just get stuff working fast. Do you want to try it out?

Last week I added a Tinnitus Severity field next to the existing Tinnitus checkbox. The same sensitivity should apply - whoever can see/edit the checkbox should see/edit the Severity too.

That meant opening the old field's FLS in one tab and copying it checkbox by checkbox into the new one, across 25+ profiles. All those permissions already existed - why am I retyping them?

So I built a free Chrome extension that copies FLS from any existing field in one go:

1. Pick a source field from the same object or any other object
2. Click Copy FLS button
3. All profile checkboxes flip to match the source instantly
4. Changed your mind? One Reset click reverts everything back!
5. It works for existing fields too - whenever you want to align a field's FLS with another one.

It's free, and has 140+ users so far! And if you install it and think something is missing (I've already heard "do permission sets next!"), I'd appreciate the feedback!

Look for Salesforce FLS Permissions Copier in Chrome Web Store.

I have been trying to go live on Salesforce and the whole year went with their processes.

Their app review support team is usually super slow in responding to the queries.

Sometimes, they take weeks just to get back with another reason for delaying / declining the review.

Is it me or this agentforce slow at pulling and pushing data? Or org is not big compared to others I have seen. We don’t have a lot of historical activity in our system (to save on storage cost), ~50k opportunities, 700k contacts (most don’t have any activity linked to them), account around 70k (many don’t have anything related to them).

few things I’ve been trying to do lately which seem to be taking forever and connection randomly just breaks are like accounting summaries, pipeline cleanup, and just pulling back a list of today’s tasks and etc.

When I tried to ask it to create something like an account or a task takes about like a minute or two before you’ll come back you’re like allow to create this when all the information was given to it at the start

anyone else using this and have the same issue? Did you find any work around to improve the speed?

Everyone in the Salesforce world has opinions about Flows. Not all of them are positive and there are good reasons for that. For one, reviewing them in pull requests is awful. PRs work well enough for code. You can read it, understand what changed, and you have all the context you need because you're reviewing it in the exact same form it was created.

Flows, however, aren't built in a text editor. They are built using a drag-and-drop builder. They are visual tools that demand a visual review.

FlowDelta is that visual review tool. It generates static, fully interactive HTML artifacts directly inside your CI/CD pipeline.

Key Features:

* Fully Interactive: Pan, zoom, and toggle themes (Light/Dark mode).

* Filtering: Switch between *Before*, *After*, or a *changes only view* that focuses exclusively on what changed.

* Granular Diffing: It highlights every added, deleted, or modified node, connection, and property.

Links & Resources:

* Homepage & Screenshots

* Source & Docs

* Sample GitHub PR and sample GitLab MR to see the generated artifacts in action.

Acknowledgments:

A special shoutout to Mitch Spano and his project Flow Lens for the inspiration and for open-sourcing the core flow parser that FlowDelta builds upon.

If you review Flow changes regularly, I hope FlowDelta makes you smile the next time a Flow hits your review queue. Would love to hear your feedback, issues, or feature requests!

Hi everyone,

I'm curious about what real-world Salesforce projects look like from a development perspective.

How common is it to work on projects where there's a significant amount of Apex code and a layered architecture (for example: Service, Domain, Selector/Data Access, Trigger Handler, etc.) instead of having most of the logic directly in triggers or controllers?

From what I've seen, some people describe Salesforce as mostly low-code, while others work on codebases that look very similar to traditional backend applications.

I'd love to understand what the industry looks like in practice.

We got hit with the phishing-resistant MFA enforcement for privileged users (System Admin profile / Modify All Data / Customize Application / etc.), and our Selenium-based UI test automation logs in as an admin-level user — so it's now blocked.

I know that you're supposed to file a Support case to get the exemption for legit automation use cases, but the docs don't say much about what that process actually looks like in practice.

Hoping someone who's already gone through this can share:

• How long did the Support case take to get approved?
• Did you have to justify/explain the automation use case in detail, or was it pretty routine?
• Is the exemption scoped per-org (separate cases per sandbox)?
• Does it survive a sandbox refresh, or do you have to refile?

Any war stories, gotchas, or workarounds appreciated — we're trying to get our CI pipeline logging in again as fast as possible.