Duplicate management is a super important part of your data plan, and helps to avoid data messes. If you aren't using duplicate and matching rules, you need to hop on the band wagon STAT. There's plenty of great reading out there on the best practices of setting up functional duplicate rules for your business — that's NOT what this article in about. I'm here to show you a nifty little invocable method I wrote to help manage duplicate data ... in flows!

One of the biggest challenges when testing is covering code that interacts with an external service. This is where the domain of unit tests ends and that of integration tests begins, but the latter is multitudes more complicated than the former. Once it’s time to test anything that makes a network call, the bar is raised.

Before you can begin building or improving Salesforce, or a related system, it’s critical that you define your requirements. We often see admins jump directly into building before spending time understanding the “why” behind a project. Unfortunately, the project almost always suffers for it.

Implementing good habits early on may be seen as (perhaps unnecessarily) adding to the entire process when first starting out with Salesforce. It is true that habit-training may indeed add hours to your work within Salesforce, but it’s totally worth it! When implemented properly, good habits will help you scale and build extremely quickly, allowing you to focus on the good problems, not the bad ones.

Salesforce Inspector is one of the most important tools to add to your stack, whether you’re inserting, updating, or deleting records.

This post was last updated 03/30/21. Introduction Time and again, we at Kicksaw have conversations with clients who are complaining about a system that’s slow, hard to use, and generally confusing. They come to us begging for help because their opportunities/accounts/etc. have become bloated and unusable.