Interface IExtraFieldCarrier

Interface implemented by carriers having Extra fields Extra fields are data typically added by plug-ins, foreignkey system and external applications

Namespace: SuperOffice.CRM.Services

Assembly: SuperOffice.Services.dll

Syntax

public interface IExtraFieldCarrier

Properties

CustomFields

Udef + Extra fields added to the carrier. Extra fields as defined by changes to database schema + user-defined fields as defined by admin. Custom fields combines user defined fields and extra fields into one bucket. The individual ExtraFields and UserDefinedFields properties are deprecated in favor of this combined collection.

Declaration

StringDictionary CustomFields { get; set; }

Property Value

Type	Description
StringDictionary

Remarks

The naming convention of the key string is as follows:

Extra field data	[Extra field name] Example: 'x_gorp' = '[I:123]'
User defined field data	[Prog-id name] Example: 'SuperOffice:1' = '[I:123]'

ExtraFields

Extra fields added to the carrier. This could be data from Plug-ins, the foreign key system, external applications, etc. The naming convention of the key string is as follows:

Plug-in data	[Plug-in name].[MainTableName name] Example: “DocumentPlugin.DocumentType”
Foreign key data	The device identity is appended directly to the device name if it exists. This is not commonly used, but the database opens for this as a possibility to have several devices with the same name, and hence we would ensure an unique key if this field is used. Example: “Audience.SecretService.DefaultCountry
User defined table data	[Table name].[Field name] Example: “Phunneling.AggregatedSales”
Other	Other data sources must ensure an unique name. If the key already exists we do not add the data to the dictionary. We also ensure that SuperOffice data are added first, so that existing data doesn’t change when more data sources are added (with duplicate data keys).

Declaration

StringDictionary ExtraFields { get; set; }

Property Value

Type	Description
StringDictionary