Raj Bhatt

Retrieve and Share Files with Agentforce Build custom Agentforce actions with Apex to fetch files from a third-party system and distribute them with publicly accessible URLs. https://lnkd.in/eFZfc-np

1

Visit our blog to explore the Salesforce Spring ’25 changes, their impacts, and how Provar ensures your testing workflows remain bulletproof. Learn more here! https://bit.ly/4ha04IA

9

Salesforce Admins, I am looking for your help (it will take 10 mins of your time). We are conducting a survey to get a better handle on the overall state of security in the Salesforce community and need your input. https://lnkd.in/gRN_bdN9 If you do take the 10 mins to complete the survey, we'll ensure you get priority access to the findings. #salesforce #salesforceadmin

5

Why reinvent the wheel and recreate reports and dashboards on the Quote object in Salesforce Revenue Cloud when you can pass primary quote data to the Opportunity object in Salesforce Sales Cloud via twin and rollup-summary fields?

8

This is a great article by the folks over at Salesforce Ben. In addition to the survey results, there is a great history of how we got here, and 5 steps for moving forward. Bravo! Ben McCarthy https://lnkd.in/gvwQp78Q

Our review of "Salesforce DevOps for Architects" by Rob Cowell and Lars Malmqvist is now live! If you are a #SalesforceDeveloper #SalesforceAdmin or #SalesforceArchitect, watch to see whether you should buy this book and what you can learn about #DevOps for #Salesforce. https://lnkd.in/eAqaQcmX

10

3 Comments

Salesforce RLM is all anyone is talking about right now. But do you know how to set up a developer environment in #RLM? Check out this short video by our own, Martin Biondi Sarra for an easy to understand and engaging step-by-step guide to get started on RLM ASAP. https://lnkd.in/ezW7Dyig #Salesforcerlm #quotetocash #developerenvironment

16

1 Comment

What you build is more important than where and how you build it. But when you're a Salesforce AppExchange partner, it actually matters a great deal how you build it—especially if you want to fully leverage the platform's extensibility. I was reminded of this when Ross Belmont commented on one of my posts a few months ago. I had asked, "What makes a great product architect?" His response stuck with me: "The humility to build your solution in the most Salesforce-y way you can, whether or not you think that's best (because admins are already used to that approach)." Admins are the unsung heroes of Salesforce, and building with them in mind makes all the difference. Here are 3 key patterns we've established at Kaptio that embrace the platform's extendability and make implementation smoother for admins: 𝟭. 𝗢𝘃𝗲𝗿𝗿𝗶𝗱𝗮𝗯𝗹𝗲 𝗙𝗹𝗼𝘄𝘀 This is one of my favorite patterns. Start with a default flow but allow it to be cloned and customized to suit specific business needs. For example, with our Package Search feature, when entering Package Search from an Account, Person Account, or Contact record, you can define a flow that pre-populates search parameters from the customer record. The default flow sets fields like currency, selling channel, and relevant tax profile, but admins can extend this to pre-populate most filters, offering them complete flexibility. 𝟮. 𝗟𝗶𝗴𝗵𝘁𝗻𝗶𝗻𝗴 𝗪𝗲𝗯 𝗖𝗼𝗺𝗽𝗼𝗻𝗲𝗻𝘁 𝗔𝘁𝘁𝗿𝗶𝗯𝘂𝘁𝗲𝘀 When designing a component, take extra time to consider what attributes admins can configure to better serve their users. I’ve been prototyping LWC components, and by using AI to brainstorm attributes, I found valuable flexibility I hadn’t thought of. One suggestion was a toggle for showing a multi-checklist for each record and embedding custom actions to trigger a flow or open another LWC. While not an immediate need, it anticipates future complexities. We use JSON for custom actions—not the most admin-friendly yet, but waiting for Salesforce to support nested attribute structures (hint, Ross Belmont!). 𝟯. 𝗘𝘅𝘁𝗲𝗻𝗱𝗮𝗯𝗹𝗲 𝗖𝗼𝗺𝗽𝗼𝗻𝗲𝗻𝘁𝘀 Sometimes you invest 40-50% of your engineering capacity in building a critical Lightning App Page, made of composable LWC components with specific behaviors. Let each component have configurable attributes (as mentioned above), but also allow admins to embed their own screen flows or custom LWCs. Enabling no-code tools within your app taps into the full potential of Salesforce’s extendability. Plus, with people like Igor Kudryk and AI code generation, admins/citizen developers will start writing components to extend your app further. As an AppExchange partner, your success often hinges on how easy you make it for admins to manage and extend your product. What other patterns have you seen that empower admins? #SalesforceAdmins #AppExchange #NoCodeSolutions

16

3 Comments

There are many approaches to Salesforce implementations and migrations. But the Crawl, Walk, Run approach is what Gail Blight and the team recommend for the greatest likelihood of success. https://lnkd.in/g2Gzw-PS

33

1 Comment

Is your Salesforce team making these common engineering mistakes? 👀 Navigating the Salesforce landscape can be tricky. That’s why we’ve identified the top 10 engineering mistakes that might be holding your team back 👇 https://grst.co/3PodhkJ

4

Is your Salesforce team making these common engineering mistakes? 👀 Navigating the Salesforce landscape can be tricky. That’s why we’ve identified the top 10 engineering mistakes that might be holding your team back: https://grst.co/3PodhkJ

3

Salesforce feature retirements you need to plan for...don't wait till last minute. Get your orgs audited and updated asap! 👉 API versions 21.0-30.0 within June 2025 👉 Workflows and Process Builder within December 2025

4

Supercharge your Salesforce deployments with peer review! 🌟 Drive quality, share knowledge, catch errors early for continuous improvement. Collaborate and excel in every deployment. Ready to unlock your team's full potential? Let's chat! 🚀 Blog - https://lnkd.in/gh7BDP87 #PeerReview #SalesforceDeployments #CodeQuality #ContinuousImprovement

5

#Agentforce builders in the #Salesforce world, I was caught out today with a little situation which isn't the most obviously documented and the UX didn't provide any reason for my error. Today, creating a custom action, none of my inputs were showing, and you cannot create an agent action without. The flow I used has variabled marked as 'available for input'. It turns out, if one of your inputs are NOT a primitive type, the agentforce custom agent action process breaks. Instead of ignoring that inout or showing you on the UI through an error message, it shows nothing. What does this mean? It means you may have to create agent specific flows and not be able to reuse the ones you already have! The docs do actually tell you after reading the small words and clicking through to a few docs - https://lnkd.in/eSADPZEZ -> https://lnkd.in/ewyyzk6a -> https://lnkd.in/eqxMJavH Watch the video below to see what I mean. Easy mistake to make, easy consideration to overlook. Poor UX with no error message made it hard to find. Posting to hopefully save the #TrailblazerCommunity time debugging but also for #Salesforce to make UX updates! P.S - I'd rather the agent action could support not primitive types for flow as otherwise, we need to create agent action specific flows and recreate the ones we have... thats not best practice, surely! Salesforce / Salesforce Admins / Salesforce Developers

50

3 Comments

🚨 PSA for anyone planning a #Salesforce data migration: 🚨 Transferring data between orgs always sounds simple on paper… Until you’re knee-deep in related records, metadata, and unexpected errors. Data migrations aren’t just about moving data; they’re about preserving relationships, accuracy, and context. Skipping steps or ignoring key dependencies can turn a "straightforward" process into a nightmare. Whether you're seeding sandboxes, merging orgs, or moving mountains of data, remember: 👉 Clean your data. 👉 Map your fields. 👉 Test, test, and test again. 👉 And yes, always account for those pesky related records and metadata! Save yourself (and your team) the headache. Be like Padmé—ask the important questions. What’s your most surprising data migration "oops" story? Share it below—we need some laughs today! 😂⬇️ #Salesforce #DataMigration #LessonsLearned #AwesomeAdmins #KeepItClean #TrailblazerCommunity

15

2 Comments

Ready to stay ahead of the curve in the ever-evolving Salesforce landscape? Dive into our recent blog featuring an exclusive interview with Bryce Baker, our Vice President of Salesforce and esteemed member of the Salesforce Revenue Cloud Partner Advisory Board. Discover how our expert knowledge and insights can help optimize your revenue lifecycle. 🚀💡 https://hubs.la/Q02C6DY50

28

Salesforce permission structures are increasingly more complex with a staggering 72% overlap in permissioning per recent industry research. 🤯 Join our CEO & Founder, Matt Meyers (CTA) alongside an esteemed panel of speakers, including Ben McCarthy, Xavery Lisinski, and Tom Hoffman, as they discuss how you can transition to a permission-set-led model, while minimizing security vulnerabilities for your org. Grab your spot for a Salesforce Ben + Elements.cloud event that you will not want to miss! https://lnkd.in/gaiN_jpi #Salesforce #SalesforceThreatProtection #DataSecurity #AwesomeAdmins #CTA #ITSecurity #Security

4

While you are super busy rolling out Salesforce features at a high pace, please note that the health of Salesforce org depends heavily on the best practices that your team follows! Salesforce implementation is usually fast-paced work. The features are lined up one after the other with a backlog that can last a few months at any point in time. The natural impact of that is the urgency of knocking features out of the door as quickly as possible and making them available for users. While we gauge the success of release with QA and UAT testing, there is one area that gets ignored. Behold the Salesforce best practices that go for a toss. By best practices, I do not (only) mean the documented ones on the Salesforce portal. I mean operational best practices. 👉 Teams tend not to review what's already built and create new components like flows or classes 👉 Naming conventions not followed for most cases - tough to determine what purpose the metadata solves 👉 Too many fields, duplicates, unused, not cleaned up. 👉 Not using utility methods and redundancy in code 👉 Random deployments without proper tracking 👉 Flows + Triggers usage to address a feature resulting in the overhead of debugging during issues 👉 Choice of Custom Metadata vs Custom Labels vs Custom Objects without proper impact analysis and ending up changing at a later point! And, ofcourse the standard best practices matter as well - however, most of the developers are conscious of those (I trust so), we are covered on that front. If you do not have someone monitoring how your team is building Metadata for new features or you are not monitoring by yourself - then I recommend slowing down a bit, talking to someone who can help manage, preparing a checklist, aligning the team and only then resume the development. As someone who likes to know what changes are being pushed into Salesforce org that I manage, I have this OCD of making sure there is nothing randomly done and each change is tangible, named appropriately, and aligns to best practices - I call it a traceability matrix! Do you as well have the OCD - let me know what your checklist looks like! Anvisol Salesforce Consulting #Salesforce #SalesforceArchitect #SalesforceConsulting #SalesforceImplementation #ITLeadership #DigitalTransformation #ITInfrastructure

3

4 Comments

The recent *Salesforce Ben* article on **how to think like a Salesforce architect** and design **multi-cloud solutions** highlights a critical aspect of future-proofing business systems. As more organizations adopt multiple Salesforce clouds to drive **sales**, **service**, **marketing**, and **commerce**, a holistic architecture strategy becomes essential to ensuring these clouds work not just in parallel, but in harmony. 💡 **What does this mean for SMBs and enterprises?** 1. **Unified Data Models Are Key**: One of the core takeaways is the importance of a **unified data strategy** across Salesforce clouds. When businesses operate in silos—where Sales Cloud doesn’t communicate effectively with Service, or Marketing is disconnected from the rest—opportunities are missed. To avoid this, architects must focus on defining common data models and governance across all clouds. For **SMBs**, this means setting up a foundation today that can evolve with your business's growth. For **enterprises**, it’s about managing complexity at scale, ensuring your entire system operates seamlessly. 2. **Scalable and Modular Design Thinking**: Architects are encouraged to design with **scalability** and **modularity** in mind. This is especially relevant as organizations often start with one or two clouds and eventually expand their Salesforce ecosystem. Building modular solutions allows businesses to introduce new clouds or integrations without a total redesign of existing infrastructure. For **enterprises**, this approach saves both time and costs over the long run. For **SMBs** looking to scale quickly, starting with a modular architecture gives flexibility to adapt and grow with confidence. 3. **APIs and Integration Best Practices**: To achieve true **multi-cloud integration**, leveraging APIs is non-negotiable. Salesforce architects must be well-versed in best practices around Salesforce's **API-led integration** as this enables systems to communicate fluidly across departments. Whether it’s enabling Marketing Cloud to draw key insights from Sales Cloud, or ensuring seamless customer support handovers from Service to Sales, proper API connectivity not only drives higher efficiency but also a more **unified customer experience**. 4. **Security and Compliance from Day One**: As your business expands across different clouds, so does your exposure to data security and compliance requirements. **Multi-cloud architecture** demands a continuous commitment to data protection, ensuring that each cloud abides by legal and industry requirements. Architects need to factor in **security protocols** across every integration, especially when sensitive information is shared across multiple teams and tools. 🔥 **The Power of a Multi-Cloud Strategy**: The ultimate goal of multi-cloud architecture is to break down silos and create a **connected enterprise**—one where customer insights flow freely, analytics are accessible across departments, and automation works seamlessly a

1