Salesforce Dictionary - Free Salesforce GlossarySalesforce Dictionary
DictionarySSolution
Core CRMBeginner

Solution

A Salesforce Knowledge-predecessor object (primarily used in Classic) that stores answers to common customer questions, searchable by agents and customers, largely replaced by Salesforce Knowledge articles in Lightning.

Solution record for a Password Reset Troubleshooting Guide with status, related product, body text, and case links.
Illustrative mock of the Solution page in Lightning Experience
§ 01

Definition

A Salesforce Knowledge-predecessor object (primarily used in Classic) that stores answers to common customer questions, searchable by agents and customers, largely replaced by Salesforce Knowledge articles in Lightning.

§ 02

In plain English

👋 Study buddy

A Solution in Salesforce is a Knowledge-predecessor object (primarily used in Classic) that stores answers to common customer questions. It's been largely replaced by Salesforce Knowledge, which provides much richer article management. Solutions are legacy; use Knowledge for new work.

§ 03

Worked example

scenario · real-world use

Brackenwell Software ran the legacy Solutions feature in Salesforce Classic from 2008 - a database of structured FAQs the support team built manually. Each Solution record had a title, problem description, and answer, all searchable from Cases. Solutions has been deprecated for years in favor of Salesforce Knowledge, which provides much richer article management (article types, page layouts, multi-language translation, validation workflows). Brackenwell's IT team is migrating their 600 Solutions to Knowledge articles. Solutions is now an archaeological feature; new orgs use Knowledge from day one.

§ 04

Why Solution matters

A Solution is a Salesforce Knowledge-predecessor object (primarily used in Classic) that stores answers to common customer questions, searchable by agents and customers. Solutions have been largely replaced by Salesforce Knowledge, which provides much richer article management, versioning, multiple article types, and multi-channel publishing.

Solutions are legacy. Any new knowledge management work should use Salesforce Knowledge. Organizations still using Solutions should plan migration to Knowledge for the richer feature set. The migration involves recreating solution content as Knowledge articles and reconfiguring search and access to use the Knowledge framework.

§ 05

How to create Solution

Solutions are the legacy Service Cloud knowledge mechanism — they're the predecessor to Lightning Knowledge. New orgs ship without Solutions; existing orgs keep them around for backward compatibility but Salesforce strongly recommends migrating to Knowledge for any net-new content.

  1. Make sure Solutions are enabled

    Setup → Solution Settings → Enable Solution Browsing. Off by default in newer orgs.

  2. Open the Solutions tab

    App Launcher → Solutions. May not be on the standard nav — admin can enable the tab.

  3. Click New

    Top-right of the list view.

  4. Enter Solution Title and Solution Details

    Title is the headline; Details is the body (rich text in HTML solutions, plain text otherwise).

  5. Pick Solution Status

    Draft / Reviewed / Duplicate. Only Reviewed solutions appear in standard solution searches.

  6. (Optional) Categorize via Solution Categories

    Setup → Solution Categories → assign this Solution to the right tree branch. Drives filtering in the Solution Browser.

  7. Submit for Review or just Save

    Save keeps it as Draft. The Solution Manager profile permission is what flips Status to Reviewed.

Mandatory fields
Solution Titlerequired

Required. The headline.

Statusrequired

Required. Draft is the default.

Gotchas
  • Solutions are deprecated. Salesforce hasn't released new functionality on this object in years and recommends Lightning Knowledge for all new orgs. Migration is one-way and requires careful planning.
  • Solutions show in search results only when Status = Reviewed. Drafts are invisible to the Solution Browser even if your profile has Read access — the Status filter is enforced.
  • Solution Categories are a separate hierarchy from Knowledge Data Categories. Don't confuse the two — Solutions use their own categorization scheme that doesn't transfer to Knowledge during migration.
§ 06

How organizations use Solution

Skyline Consulting

Migrates legacy Solutions to Salesforce Knowledge articles for modern knowledge management.

NovaScale

Treats Solution references as legacy migration triggers.

CloudNine Solutions

Uses Salesforce Knowledge for all knowledge management work.

§

Trust & references

Official documentation

Straight from the source - Salesforce's reference material on Solution.

Was this entry helpful?
Help us write better definitions. Quick reactions or detailed edit suggestions.
§

Test your knowledge

Q1. What is a Solution?

Q2. What replaces Solutions?

Q3. Should you create new Solutions?

§

Discussion

Loading…

Loading discussion…