Solution Junkies’ Post

Fascinating. And lots of handy tips. I’ve seen a few successful ones for scale regular giving fundraising use cases. Some of the reasons are in the comments below. Although one isn’t - the depth of fundraising knowledge in your implementing partner.

Has anyone had a successful Salesforce implementation? Or one that would have been except for one thing? My definition of success is that there's no undercurrent of grumblings or a theme of "Salesforce isn't configured correctly" or "overpriced" I'll admit, I've only went through one implementation, and that was in 2010. It was so successful I reimplemented it a year later. Since then, I've come behind many implementations and have yet to encounter a happy story the first time around. I hear it every day on LinkedIn and Slack as well. So I'm curious, to hear your thoughts, if you rocked it out of the park, what did you all do differently? #salesforce #salesforcearchitects #salesforceadmins #businesssystems

😫 We engaged Salesforce on 30th January 2024 for a 6-12 week build, and we are still awaiting the final product. After chatting with industry colleagues, it seems this delay is common when working with Salesforce. 🤕 🙏 Have you encountered similar delays or successfully resolved substantial delays with Salesforce? Your insights would be greatly appreciated! Feel free to send me a direct message. #Salesforce #ProjectDelays #IndustryInsights

🚀 Hey Salesforce Developers, While working in Salesforce, you must have faced challenges while implementing pagination. Here is a video that covers: 1. Client-side pagination 2. Server-side pagination with datatable 3. Server-side pagination without datatable You'll also find code to help you implement these solutions. Video link - https://lnkd.in/ex-TPJwH #Salesforce #SalesforceDevelopment #Pagination #PaginationinLWC #ForceFellow

If I had to pick some of the most annoying things in #Salesforce 1️⃣ LastModifiedDate changes when user saves, regardless of any field being actually changed or not. With nasty side effects. Does this serve any fruitful purpose? 2️⃣ No native method (in my knowledge at least) to get DIRECTLY just the list of changed fields during an update. Ok this is more reasonable, but still annoying 3️⃣ Native debug logs navigation and reliability The fatigue is real

I don't know why I have become so obsessed with Salesforce's bulk API over the years. Seriously, I have no clue, but I just always find my self reaching for it. Many times I've had to explain the ins and outs of this funky little API to non-Salesforce developers. This often starts with me sending a link to Salesforce's docs, which I think we can all agree, could use some work. I don't know why they can't use something like the Open API (Swagger) format to document their APIs. I really like the Open API spec because it make it really easy for developers to read and reason about the API. It also make it simple for machines to ingest so you can do things like virtualize it in an API Gateway with just a few clicks. So after searching (I think I did one google search, lol) and not seeing that anyone has Swaggerified the Bulk API 2.0 sufficiently, I thought I would give it a go and share it with the world. I did my best to include lots of descriptions and examples. It includes both `Bulk Ingest` as well as `Bulk Query` Here's a link to the github repo. I'd really appreciate some ⭐s, and any feedback you have! https://lnkd.in/gujSKW6Z Thanks! #Salesforce #SalesforceDevelopers #SalesforceAdmins #API #OpenAPI #Swagger

Working on style updates for the org detail screen: 1: Added Instance Details (status, instance name, release ver/#, Maint Window) 2: Display limit metrics historically (15min increments) #awesomeadmins #salesforce #laravel

Is it impossible for newcomers to break into the Salesforce ecosystem? No, but it’s significantly more competitive now. Even for seasoned professionals, it’s time to level up. Read my article on Salesforce Ben about leveling up. Link is in the comments! #Salesforce #Admineloper #AlwaysBeLearning #CareerDevelopment

📌#WhatsInItForYou! #59📌 Today let's explore one of the interesting features getting released as part of Salesforce Summer' 24 i.e., Lock and Unlock records action in Flow 🔐 🤠 Yes, you heard it. With the Summer '24 release, we are going to have a native Lock Record Action which is used to lock or unlock the record directly within the flow ✨ Before Summer'24, the only way to lock the entire record is to use Apex [Approval Methods - Approval.lock(recordId)] or create an Approval process on that object. A bit painful...right? 😪 How to Configure the Lock Record action in flow 🤔 👉 Action - Specifies the action to perform on the record. Valid values are Lock and Unlock. 👉 Record ID - The ID of the record to be locked or unlocked. 👉 Allowed ID - The ID of a user, group, queue, or user role record that represents who can edit the record while it's locked. With the simple sample use case, let's see this flow gem in action 😎 🗒 If the opportunity record is closed (Closed Won/ Closed Lost), none of the Sales Reps should be able to edit the record. 📌 Solution: Create a Record Triggered (After-Save) flow on Opportunity, set the condition as 'isClosed' Equals 'True', add the Lock Record action, and set the appropriate parameters like Action as Lock and Record ID as triggering recordId. Save the flow, debug, and activate it. Note: Lock Record action is not available in the Before-Save Record Triggered flow. The content I've shared is for informational purposes only and represents my personal perspective, not necessarily that of Salesforce company. #SalesforceTips #Salesforce #Tips #LearningandGrowing #Trailblazer #SalesforceDevelopers #SalesforceConsultant #SalesforceOhana #Salesforceadmins #TechnicalConsultant #AwesomeAdmins #Architect #DaringDevelopers #ConfidentConsultant #SalesforceCommunity #Connections #SalesforceLearning #Flowsome #Flow #ReleaseReadiness

Check out this great article in Salesforce Ben by my friend Jennifer O.!