SALEROLE: Role
The SALEROLE entity: A buyer role in the sales methodology, linking to pain points, talking points, and weighted products for that persona.
Default definition. This article describes the default
SALEROLE 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 SALEROLE.Entity properties
| Property | Value |
|---|---|
| Entity code | SALEROLE |
| Display name | Role |
| Plural | Roles |
| Level | 30000 |
Use cases
SALEROLE defines a buyer persona or role within a target market. It is the central node in the sales methodology graph: markets (SALEMARKET) link to roles, and each role links to both pain points (SALEPAIN) and talking points (SALETALK) via multi-link relationships displayed as relatedlists. Products weighted against this role are shown via SALEPRODROL junction entity queried on comboKey2.
This four-column layout (role details, pains, talking points, products) gives sales reps a complete playbook for engaging a specific buyer persona.
Fields
Basics
| Field | Type | Required | Notes |
|---|---|---|---|
name | text | Yes | Role name |
description | text (multi-line) | Description |
Relationships
- Related lists:
SALEPAIN(formatlink),SALETALK(formatlink),SALEPRODROL(formatSUB|SALEROLE).
Creating a Role via the API
POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json
{
"entity": "SALEROLE",
"level": 30000,
"comboKey": "SUB:|ENT:",
"name": "Example name",
"description": "Example Description"
} Listing Roles records
GET /v1/entities/SALEROLE/SUB