A field-sales territory seat that exists independently of whoever currently holds it. Visit routes (beats) can be owned by a position instead of a person: plans generated from them go to the seat's holder at generation time, and the route's Resource is kept equal to that holder. Who holds the seat, and when, is recorded in Resource Position records; saving one moves the seat's routes and open future plans to the new holder, and a daily job (when the Position-based route assignment setting is on) applies future-dated handovers. The seat's Operating Location is the start and end point for territory planning, so a handover never moves the territory. Assignment rules can give records to a position's current holder. There is no numbering, status or approval.
Fields
| Field | Label | Type | Required | What it does |
|---|
BranchId | Branch | Lookup → Branch | | The branch the seat belongs to. An administrative grouping, and the fallback start point for territory planning when Operating Location is empty. It does not decide which routes or outlets the seat has. |
Code | Code | MultiLineText | | Optional short code for the seat (up to 50 characters). Assignment rules can find a position by its code. |
CreatedById | Created By | Lookup → UserAccount | Yes | |
CreatedDateTime | Created Date | DateAndTime | | |
Description | Description | Text | | Free-text notes about the seat. Not used by any process. |
GeoLocation | Operating Location | GeoLocation | | The seat's operating base on a map: territory planning starts and ends the seat's beats here. When it is empty, the seat's branch location is used instead. |
Id | Id | Guid | Yes | |
IsActive | Active | Boolean | | Whether the seat is in use; on by default. Only assignment rules check it (an inactive position is never matched). Plan generation and territory planning ignore it, so an inactive seat still owns its routes and generates plans. |
ModifiedById | Modified By | Lookup → UserAccount | Yes | |
Name | Name | Text | | The seat's name, shown in pickers and territory-planning messages. Name the seat, not the person. Assignment rules can find a position by its name. |
OwnerId | Owner | Lookup → UserAccount | Yes | |
ParentPositionId | Parent Position | Lookup → Position | | The seat this one reports to, for reference. Nothing reads it: it gives no visibility, approval or reporting rights over the seats below. |
RecordTypeId | Record Type | Guid, hidden | | |
UIProps | UI Props | Text | | |
UpdatedDateTime | Modified Date | DateAndTime | | |
Actions
| Action | Label | Type | What it does |
|---|
BulkDelete | Delete | Delete | Delete the selected records. |
Delete | Delete | Delete | Delete |
DeleteInList | Delete | Delete | Delete in a list page |
Edit | Edit | Edit | Edit |
EditInLine | Edit | EditInline | Edit in page. |
EditInList | Edit | EditInline | Edit In List Header |
New | New | New | New |
