ReasonSold table - SuperOffice

ReasonSold Table (115)

ReasonSold MDO list item table. Why was the sale marked as sold (why did we succeed)

Fields

Name	Description	Type	Nullable
ReasonSold_Id	Primary key	PK	No
name	The list item	String(239)	No
rank	Rank order	UShort	Yes
tooltip	Tooltip or other description	String(254)	Yes
deleted	0 -> record is active 1 -> record is ‘deleted’ and should not be shown in lists	UShort	Yes
registered	Registered when	UtcDateTime	No
registered_associate_id	Registered by whom	FK associate	No
updated	Last updated when	UtcDateTime	No
updated_associate_id	Last updated by whom	FK associate	No
updatedCount	Number of updates made to this record	UShort	No

Indexes

Fields	Types	Description
name	String(239)	Unique

Relationships

Table	Description
associate	Employees, resources and other users - except for External persons
ReasonSoldGroupLink	User group link table for ReasonSold, for MDO item hiding
ReasonSoldHeadingLink	Heading link table for ReasonSold, for MDO headers
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.
SaleHist	Mirror image of the Sale table, providing a full transaction history. Every time you edit a sale, the current record of the sale is also saved here.

Replication Flags

Replicate changes DOWN from central to satellites and travellers.
Replicate changes UP from satellites and travellers back to central.
Copy to satellite and travel prototypes.

Security Flags

No access control via user’s Role.

Related topics

ReasonSoldHeadingLink table ReasonSoldGroupLink table SuperOffice.WebApi.Data.ReasonSold SuperOffice.WebApi.Data.SaleEntity Get Reason Sold Put Reason Sold