SALEPAIN: Pain
The SALEPAIN entity: A buyer pain point in the sales methodology, describing a problem experienced by a buyer role.
Default definition. This article describes the default
SALEPAIN definition shipped with DemandFlow. Administrators can add, remove, rename, or re-type fields, change which ones are required, and alter the layout from the Definitions screen in Settings. Your tenant's current schema may differ from what is shown here. To read the current definition at any time, GET the DEFINITION object whose id matches SALEPAIN.Entity properties
| Property | Value |
|---|---|
| Entity code | SALEPAIN |
| Display name | Pain |
| Plural | Pains |
| Level | 30000 |
Use cases
SALEPAIN captures specific pain points that buyer roles experience, forming a key part of the sales methodology hierarchy (Market -> Role -> Pain -> Solution). Pain points are linked to SALEROLE via a multi-link relationship visible on the SALEROLE record, and to SALESOL (solutions) and SALEREL (related pains) via objectLookup references from those entities. Products weighted against this pain are shown via SALEPRODPAN junction entity queried on comboKey2.
Fields
Basics
| Field | Type | Required | Notes |
|---|---|---|---|
name | text | Yes | Summary |
description | text (multi-line) | Description |
Relationships
- Related lists:
SALEPRODPAN(formatSUB|SALEPAIN).
Creating a Pain via the API
POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json
{
"entity": "SALEPAIN",
"level": 30000,
"comboKey": "SUB:|ENT:",
"name": "Example name",
"description": "Example Description"
} Listing Pains records
GET /v1/entities/SALEPAIN/SUB