Conditional Formatting in Salesforce Without Code or Formula Fields

Written by

Peter Gascoyne

November 20, 2026

Conditional formatting rules in a Salesforce grid, Grids 6.79 by RavenApps

Grids 6.79 brings conditional formatting into Salesforce, built by the people using the grid. Highlight cells or rows on value, combine conditions with custom logic, and preview rules against live data before saving.

Summary

Grids by RavenApps now does conditional formatting inside Salesforce, built by the people who use the grid rather than by an admin. Highlight a cell or a whole row based on its values, combine conditions with All, Any or custom logic, and preview the rules against live data before you save them.

‍

No formula fields. No custom code. No deployment. Available in Grids 6.79.

‍

Why did we build this?

Conditional formatting in Salesforce has always been possible, and it has always been somebody else's job.

‍

The standard route is a formula field that returns an image or a coloured label, built in Setup by an admin, deployed, and then maintained forever. Every new rule is a new field. Every change to a threshold is a change request. And the result sits in its own column rather than colouring the data it describes.

‍

Meanwhile the person who actually needs the highlight is a sales manager looking at a pipeline on a Monday morning, who wants overdue close dates in red and cannot wait two weeks for a field.

‍

So we moved it. Rules now live in the grid, are built by the user looking at the data, and take effect immediately.

‍

What is conditional formatting in Grids?

It is a set of rules attached to a grid that change how cells or rows are displayed based on the values in them. Open the grid, define a condition, pick a format, and matching records change appearance.

‍

Spotting what matters is the whole point. A few examples that teams set up in the first ten minutes:

  • Overdue close dates in red
  • Deals closing today in amber
  • Anything over a value threshold in bold
  • Cases breaching SLA with a warning icon
  • Records missing a required field, so the gaps are visible rather than hunted for

‍

Highlight a cell or the whole row

Each rule targets either the cell holding the value or the entire row. Cell formatting is better when you are scanning one column, for example a close date or an amount. Row formatting is better when the condition describes the record rather than the field, for example an at-risk opportunity.

‍

Conditions across the field types you actually use

Rules work on text, number, date, picklist and checkbox fields. Conditions combine with All, Any, or custom logic written the way Salesforce writes it, so 1 AND (2 OR 3) does what you expect.

‍

That custom logic line matters more than it sounds. Most real highlighting rules are not a single comparison. "Closing this quarter AND over fifty thousand AND not already in Negotiation" is a normal request, and a formula field route turns it into a ticket.

‍

Relative dates

Date conditions take relative values such as Today or N days ago, rather than hard-coded dates that go stale the day after you set them. A rule that says "close date before today" stays correct forever without anyone touching it.

‍

Eight format presets, plus bold and icons

Formatting is deliberately a short list rather than a colour picker. Eight presets, bold text, and icons. The constraint is intentional: a grid where every rule picks its own shade of green stops communicating anything. A small palette keeps red meaning one thing across every grid in the org.

‍

Preview before you save

Rules are previewed against the grid's live data before they are saved, including a live count of how many rows match. If a rule you thought was an exception turns out to match four hundred records, you find out while you are writing it rather than after everyone has been looking at a wall of red for a week.

‍

That count is a quiet quality check on the rule itself. Formatting that matches most of the grid is not formatting, it is a background colour.

‍

Formatting survives hover

A small fix with an outsized effect: formatting stays visible when you hover over a row. Previously the hover state covered the thing the user was looking for, which is exactly the wrong moment for a highlight to disappear.

‍

How is this different from a formula field?

Formula fields are still the right answer when the value itself needs to exist in Salesforce, for example something reports group by or automation reads. The differences day to day are these:

  • Who builds it: a formula field is an admin task in Setup. A grid rule is built by the end user, in the grid, in about a minute.
  • Where it appears: a formula field is an extra column. A rule colours the data already on screen, so nothing is added to the layout.
  • Cost of change: changing a threshold on a formula field means editing and redeploying a field used elsewhere. Changing a rule means editing a rule.
  • Field count: highlighting rules built as formula fields accumulate. Objects have field limits, and a dozen display-only formulas is a poor use of them.
  • Combining conditions: nesting several conditions into one formula field is possible and unpleasant. Custom logic in the rule builder is a line of text.

‍

What it is not for

Worth being clear about the edges. Conditional formatting is a display feature. It does not change data, trigger automation, or feed reports, so if a business process depends on the state being recorded, that still belongs in a field, a Flow or a validation rule.

‍

What it does is make the exceptions on a screen findable in a glance rather than by reading, which turns out to be most of what people wanted the formula fields for anyway.

‍

How to get started

  1. Install or upgrade via the AgentExchange listing or the Package Version page.
  2. Add Conditional Formatting to the Action picklist on the Grid object, under Setup, Object Manager, Grid.
  3. Add it to the Action field on each grid that should offer it.
  4. Open a grid, create a rule, and watch the match count as you write it.

‍

Existing grids are unaffected until you add the action. Grids is free in sandboxes, with full features and no time limit, so you can build your rules against your own data before deciding anything.

‍

Useful Links

‍

Thank You

Thanks to everyone who asked for this one, and in particular to the people who sent us screenshots of their formula field workarounds. If there is a feature you need, tell us, because the roadmap is shaped by customers. Book a Call or Contact Us.

In this article:
Boost Salesforce Productivity with Grids & DocGen

40+ features to power up your workflows

Discover Grids
Discover DocGen
"A must have tool for efficient data management"

Alex Andony, Truly Investor Capital

AppExchange

Start working smarter in Salesforce