3 levels of using hardcoded values in flows

Every once in a while, you’ll need to use static variables in a Salesforce automation. These variables may be different in sandboxes and in production. But once they are set in a sandbox, they don’t change often.

To illustrate the option, imagine a simple example where we want to assign accounts to a specific user.… Read the rest

You really don’t want to rename standard objects

There’s a temptation that just because you can rename standard objects, you should. Common examples are

  • Contact –> Person
  • Account –> Company
  • Opportunity –> Project

Here are several reasons why this is a bad idea.

1. Inconsistency
It’s generally bad design practice to have the label and API name be different.… Read the rest

The larger impact of merging records

Salesforce offers a few options to merge records, whether they be accounts or contacts.

The merging process is straightforward for the user; you choose which record becomes the master, and merge individual fields into the master. All related objects of the merged records are reparented, and then merged records are deleted.… Read the rest

Naming your project champion

My coaching students often ask me what is usually the biggest concern about a Salesforce project. You know, the one that often keeps me up at night, worrying.

The answer usually surprises them, because it has nothing to do with technology.… Read the rest

How much data should you migrate?

Let’s imagine, as part of a new Salesforce implementation, you need to migrate data from a legacy system. The legacy system contains people and companies and sales opportunities. So, how much data should you migrate?

Most organizations will want all the accounts and contacts, regardless of when the last contact or activity was.… Read the rest

At least three rounds of data migration

Let’s imagine, as part of a new Salesforce implementation, you need to migrate data from a legacy system. Let’s also assume the data can be exported into a .csv file. So, how many rounds of data migration should you do?

Since the title gives away the answer, let’s discuss the rationale.… Read the rest

Should you only update the source of truth?

Let’s imagine a scenario in which Salesforce needs to integrate with a system of record for account information.

This system, which we’ll call AccountSOT, is the “source of truth” for some account-related fields. This includes the account name, addresses, phone numbers, and FAXs (don’t laugh, some companies still use them).… Read the rest

Why you shouldn’t use tags in Salesforce

Initially, tagging records seems like a good idea. And, in theory, it is. In practice however, not so much.

In Salesforce, tags are called topics. You can add the topic component to any lightning page, and then configure some basic settings such as the title, placeholder text, and number of topics shown.… Read the rest

The benefits of hypercare

The first time I heard the word “hypercare”, I thought it was a nonsensical word. I quickly grouped it with other “hyper” words, like hyperforce, hyperspeed, and hyper-ridiculous.

After learning what it actually means and why it exists, I started offering it on all my Salesforce projects.… Read the rest

What is the iron triangle?

Salesforce projects, along with most other projects, work within three main constraints:

  1. Scope (features/capabilities)
  2. Time (schedule)
  3. Cost (resources & budget)

These are also known as the iron triangle, which you have to admit sounds a whole lot cooler than just saying, “three constraints”.… Read the rest

Center of Excellence: Security

The last pillar of a Salesforce Center of Excellence is security. Here are three main considerations for security:

1. New/Old Users

With a small org, it’s common for new users to be manually added and maintained. When a user leaves the organization, they can be manually frozen or deactivated.… Read the rest

Center of Excellence: Metadata Management

Knowing how you will manage metadata is the next pillar of the Salesforce Center of Excellence. Here are three many considerations.

1. Source Code Repository

When you have a small org, it’s OK to start building metadata in a single instance, say a Development (DEV) sandbox.… Read the rest

Center of Excellence: Leadership

Nothing happens without leadership. It’s the staff at the helm of the ship that drives projects forward. Without them, everyone would randomly bump into each other, like bumper cars at the arcade.

Here are three important roles of leadership within a Center of Excellence.… Read the rest

Center of Excellence: Architecture

The architecture pillar of the Salesforce Center of Excellence is a massive conversation. Setting up the architecture team and For now, let’s focus on three topics.

1. Data Modeling

One of my favorite expressions in construction is “measure twice and cut once”.… Read the rest

Center of Excellence: Change Management

Heraclitus, a Greek philosopher, is quoted as saying, “change is the only constant in life.” Despite being so common, people often resist change.

So in the context of a Salesforce Center of Excellence, the Change Management Office (CMO) is responsible for warming the audience to the upcoming change and supporting their needs.… Read the rest

Center of Excellence: Tooling

Selecting the proper tools is one of my personal favorite pillars of the Center of Excellence. Here are three themes regarding tooling:

1. When to Build vs Buy

One of the first questions to ask is, under what conditions should you build a custom piece of functionality or buy an existing product?… Read the rest

Center of Excellence: Methodology

The methodology pillar, as part of a Center of Excellence, is about defining the delivery process. Let’s focus on three core topics of this pillar.

1. How to Deliver

This step is about determining how projects will be delivered. What business processes will projects use, how DevOps is weaved into the conversation, and .… Read the rest

Center of Excellence: Governance

One of the most important responsibilities of a Center of Excellence is setting up a proper governance framework.

In short, governance is a system of rules and processes that a company creates. It determines who has power and accountability, and who makes decisions.… Read the rest

Center of Excellence: Standards

Establishing and maintaining standards are important in a Salesforce org. They determine the basic rules of an implementation, so it doesn’t look like it was built by 3 admins and 2 devs.

Here are three core ingredients to build standards in a Salesforce CoE:

1.Read the rest

Center of Excellence: Vision

Vision is about the art of the possible. There are three main components to focus on.

1. Business Goals

Too many agencies focus on the wrong problem to solve. They focus on the inputs instead of the outputs. The number of hours something will take instead of what are the business goals.… Read the rest

Center of Excellence: PMO

Out of all the pillars in a Center of Excellence, the Project Management Office (PMO) is the one I’m least familiar with. So if any of my PM readers want to add to anything I say, please chime in 🙂

In a Salesforce context, three main functions of the PMO is:

1.Read the rest

Center of Excellence: Prototyping

In short, prototyping is the innovation hub that builds out Salesforce prototypes to show the “art of the possible”

This can be broken down into three main components:

1. User flow

It’s important that user’s know and understand how they will be using Salesforce.… Read the rest