SaleStakeholder Table (121)
Stakeholders in the sale, very similar to project members
Fields
| Name | Description | Type | Null |
|---|---|---|---|
| salestakeholder_id | Primary key | PK | |
| sale_id | Parent sale | FK sale | ● |
| contact_id | Contact ID of person or contact who is the sale stakeholder | FK contact | ● |
| person_id | Person ID of person who is the sale stakeholder, or 0 if it’s just a contact | FK person | ● |
| rank | Rank in list | UShort | ● |
| stakeholderrole_id | Member type link | FK StakeholderRole | ● |
| comment | Optional comment | String(2047) | ● |
| registered | Registered when | UtcDateTime | |
| registered_associate_id | Registered by whom | FK associate | |
| updated | Last updated when | UtcDateTime | |
| updated_associate_id | Last updated by whom | FK associate | |
| updatedCount | Number of updates made to this record | UShort |
Indexes
| Fields | Types | Description |
|---|---|---|
| salestakeholder_id | PK | Clustered, Unique |
| contact_id | FK | Index |
| person_id | FK | Index |
Relationships
| Table | Description |
|---|---|
| associate | Employees, resources and other users - except for External persons |
| contact | Companies and Organizations. |
| person | Persons |
| sale | Sales For every Sale record edited through the SuperOffice GUI, a copy of the current version of the record will be saved in the SaleHist table. This also applies to editing done through the SaleModel COM interface, but not to editing done through the OLE DB Provider or other channels. |
| StakeholderRole | Role a stakeholder has in a sale |
Replication Flags
- Area Management controlled table. Contents replicated to satellites and traveller databases.
- Replicate changes UP from satellites and travellers back to central.
- Copy to satellite and travel prototypes.
- Cache table during filtering.
Security Flags
- Sentry controls access to items in this table using user’s Role and data rights matrix on the table’s parent.