Class DocumentTags

Substitution tags for a document, based on data from a IDocumentInfo

Inheritance
object
TagContainer
DocumentTags
Inherited Members
Namespace: SuperOffice.CRM.Globalization
Assembly: SoDataBase.dll
Syntax
public class DocumentTags : TagContainer
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

Constructors

DocumentTags(int)

Substitution tags for a document, based on data from a IDocumentInfo

Declaration
public DocumentTags(int documentId)
Parameters
Type Name Description
int documentId
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

Fields

_document

Substitution tags for a document, based on data from a IDocumentInfo

Declaration
protected IDocumentInfo2 _document
Field Value
Type Description
IDocumentInfo2
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

Properties

AppointmentId

Appointment ID

Declaration
[TemplateTag("apid")]
public int AppointmentId { get; }
Property Value
Type Description
int
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

Attention

Selected contact in the Document dialog or text that is specified in the Company field for a recipient of the document

Declaration
[TemplateTag("attn")]
public string Attention { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

Date

Date in short format, e.g. 10.12.01

Declaration
[TemplateTag("sdat")]
public string Date { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

DateLong

Date in long format, e.g. 10 December 2001

Declaration
[TemplateTag("date")]
public string DateLong { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

DateLongSpecial

Date in special long format, e.g. 10 December 2001

Declaration
[TemplateTag("dat1")]
public string DateLongSpecial { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

Description

Description of the created document

Declaration
[TemplateTag("desc")]
public string Description { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

Document

Substitution tags for a document, based on data from a IDocumentInfo

Declaration
protected IDocumentInfo2 Document { get; }
Property Value
Type Description
IDocumentInfo2
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

FileName

Name of the document, without the path (e.g. SUPER001.DOC)

Declaration
[TemplateTag("file")]
public string FileName { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

Header

The heading for the created document

Declaration
[TemplateTag("head")]
public string Header { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

Id

Document ID (hidden, unique ID)

Declaration
[TemplateTag("doid")]
public override int Id { get; }
Property Value
Type Description
int
Overrides
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

OurReference

Our reference

Declaration
[TemplateTag("oref")]
public string OurReference { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

PublishActiveDate

Publish active date Not supported

Declaration
[TemplateTag("dopa")]
public string PublishActiveDate { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

PublishEndDate

End date for publishing Not supported

Declaration
[TemplateTag("dope")]
public string PublishEndDate { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

PublishStartDate

Start date for publishing Not supported

Declaration
[TemplateTag("dops")]
public string PublishStartDate { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

Salutation

Salutation as entered, or created automatically from the contact (Mr/Ms and last name)

Declaration
[TemplateTag("salu")]
public string Salutation { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

SerialNumber

Ascending serial number (different for every template)

Declaration
[TemplateTag("snum")]
public string SerialNumber { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

SuggestedDocumentId

The document's SuggestedDocument Id. 0 if document is not part of a sale/project guide.

Declaration
[TemplateTag("dsug")]
public int SuggestedDocumentId { get; }
Property Value
Type Description
int
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

Time

Time in short format, e.g. 12:10

Declaration
[TemplateTag("time")]
public string Time { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldDecimal1

Userdefined field 1 of type decimal

Declaration
[TemplateTag("df01")]
public string UserDefinedFieldDecimal1 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldDecimal10

Userdefined field 01-10 of type decimal

Declaration
[TemplateTag("df10")]
public string UserDefinedFieldDecimal10 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldDecimal2

Userdefined field 2 of type decimal

Declaration
[TemplateTag("df02")]
public string UserDefinedFieldDecimal2 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldDecimal3

Userdefined field 01-10 of type decimal

Declaration
[TemplateTag("df03")]
public string UserDefinedFieldDecimal3 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldDecimal4

Userdefined field 01-10 of type decimal

Declaration
[TemplateTag("df04")]
public string UserDefinedFieldDecimal4 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldDecimal5

Userdefined field 01-10 of type decimal

Declaration
[TemplateTag("df05")]
public string UserDefinedFieldDecimal5 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldDecimal6

Userdefined field 01-10 of type decimal

Declaration
[TemplateTag("df06")]
public string UserDefinedFieldDecimal6 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldDecimal7

Userdefined field 01-10 of type decimal

Declaration
[TemplateTag("df07")]
public string UserDefinedFieldDecimal7 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldDecimal8

Userdefined field 01-10 of type decimal

Declaration
[TemplateTag("df08")]
public string UserDefinedFieldDecimal8 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldDecimal9

Userdefined field 01-10 of type decimal

Declaration
[TemplateTag("df09")]
public string UserDefinedFieldDecimal9 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldInt1

Userdefined field 1 of type integer

Declaration
[TemplateTag("dl01")]
public string UserDefinedFieldInt1 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldInt10

Userdefined field 01-60 of type integer

Declaration
[TemplateTag("dl10")]
public string UserDefinedFieldInt10 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldInt11

Userdefined field 01-60 of type integer

Declaration
[TemplateTag("dl11")]
public string UserDefinedFieldInt11 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldInt12

Userdefined field 01-60 of type integer

Declaration
[TemplateTag("dl12")]
public string UserDefinedFieldInt12 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldInt13

Userdefined field 01-60 of type integer

Declaration
[TemplateTag("dl13")]
public string UserDefinedFieldInt13 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldInt14

Userdefined field 01-60 of type integer

Declaration
[TemplateTag("dl14")]
public string UserDefinedFieldInt14 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldInt15

Userdefined field 01-60 of type integer

Declaration
[TemplateTag("dl15")]
public string UserDefinedFieldInt15 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldInt16

Userdefined field 01-60 of type integer

Declaration
[TemplateTag("dl16")]
public string UserDefinedFieldInt16 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldInt17

Userdefined field 01-60 of type integer

Declaration
[TemplateTag("dl17")]
public string UserDefinedFieldInt17 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldInt18

Userdefined field 01-60 of type integer

Declaration
[TemplateTag("dl18")]
public string UserDefinedFieldInt18 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldInt19

Userdefined field 01-60 of type integer

Declaration
[TemplateTag("dl19")]
public string UserDefinedFieldInt19 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldInt2

Userdefined field 2 of type integer

Declaration
[TemplateTag("dl02")]
public string UserDefinedFieldInt2 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldInt20

Userdefined field 01-60 of type integer

Declaration
[TemplateTag("dl20")]
public string UserDefinedFieldInt20 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldInt21

Userdefined field 01-60 of type integer

Declaration
[TemplateTag("dl21")]
public string UserDefinedFieldInt21 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldInt22

Userdefined field 01-60 of type integer

Declaration
[TemplateTag("dl22")]
public string UserDefinedFieldInt22 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldInt23

Userdefined field 01-60 of type integer

Declaration
[TemplateTag("dl23")]
public string UserDefinedFieldInt23 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldInt24

Userdefined field 01-60 of type integer

Declaration
[TemplateTag("dl24")]
public string UserDefinedFieldInt24 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldInt25

Userdefined field 01-60 of type integer

Declaration
[TemplateTag("dl25")]
public string UserDefinedFieldInt25 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldInt26

Userdefined field 01-60 of type integer

Declaration
[TemplateTag("dl26")]
public string UserDefinedFieldInt26 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldInt27

Userdefined field 01-60 of type integer

Declaration
[TemplateTag("dl27")]
public string UserDefinedFieldInt27 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldInt28

Userdefined field 01-60 of type integer

Declaration
[TemplateTag("dl28")]
public string UserDefinedFieldInt28 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldInt29

Userdefined field 01-60 of type integer

Declaration
[TemplateTag("dl29")]
public string UserDefinedFieldInt29 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldInt3

Userdefined field 01-60 of type integer

Declaration
[TemplateTag("dl03")]
public string UserDefinedFieldInt3 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldInt30

Userdefined field 01-60 of type integer

Declaration
[TemplateTag("dl30")]
public string UserDefinedFieldInt30 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldInt31

Userdefined field 01-60 of type integer

Declaration
[TemplateTag("dl31")]
public string UserDefinedFieldInt31 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldInt32

Userdefined field 01-60 of type integer

Declaration
[TemplateTag("dl32")]
public string UserDefinedFieldInt32 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldInt33

Userdefined field 01-60 of type integer

Declaration
[TemplateTag("dl33")]
public string UserDefinedFieldInt33 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldInt34

Userdefined field 01-60 of type integer

Declaration
[TemplateTag("dl34")]
public string UserDefinedFieldInt34 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldInt35

Userdefined field 01-60 of type integer

Declaration
[TemplateTag("dl35")]
public string UserDefinedFieldInt35 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldInt36

Userdefined field 01-60 of type integer

Declaration
[TemplateTag("dl36")]
public string UserDefinedFieldInt36 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldInt37

Userdefined field 01-60 of type integer

Declaration
[TemplateTag("dl37")]
public string UserDefinedFieldInt37 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldInt38

Userdefined field 01-60 of type integer

Declaration
[TemplateTag("dl38")]
public string UserDefinedFieldInt38 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldInt39

Userdefined field 01-60 of type integer

Declaration
[TemplateTag("dl39")]
public string UserDefinedFieldInt39 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldInt4

Userdefined field 01-60 of type integer

Declaration
[TemplateTag("dl04")]
public string UserDefinedFieldInt4 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldInt40

Userdefined field 01-60 of type integer

Declaration
[TemplateTag("dl40")]
public string UserDefinedFieldInt40 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldInt41

Userdefined field 01-60 of type integer

Declaration
[TemplateTag("dl41")]
public string UserDefinedFieldInt41 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldInt42

Userdefined field 01-60 of type integer

Declaration
[TemplateTag("dl42")]
public string UserDefinedFieldInt42 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldInt43

Userdefined field 01-60 of type integer

Declaration
[TemplateTag("dl43")]
public string UserDefinedFieldInt43 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldInt44

Userdefined field 01-60 of type integer

Declaration
[TemplateTag("dl44")]
public string UserDefinedFieldInt44 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldInt45

Userdefined field 01-60 of type integer

Declaration
[TemplateTag("dl45")]
public string UserDefinedFieldInt45 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldInt46

Userdefined field 01-60 of type integer

Declaration
[TemplateTag("dl46")]
public string UserDefinedFieldInt46 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldInt47

Userdefined field 01-60 of type integer

Declaration
[TemplateTag("dl47")]
public string UserDefinedFieldInt47 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldInt48

Userdefined field 01-60 of type integer

Declaration
[TemplateTag("dl48")]
public string UserDefinedFieldInt48 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldInt49

Userdefined field 01-60 of type integer

Declaration
[TemplateTag("dl49")]
public string UserDefinedFieldInt49 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldInt5

Userdefined field 01-60 of type integer

Declaration
[TemplateTag("dl05")]
public string UserDefinedFieldInt5 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldInt50

Userdefined field 01-60 of type integer

Declaration
[TemplateTag("dl50")]
public string UserDefinedFieldInt50 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldInt51

Userdefined field 01-60 of type integer

Declaration
[TemplateTag("dl51")]
public string UserDefinedFieldInt51 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldInt52

Userdefined field 01-60 of type integer

Declaration
[TemplateTag("dl52")]
public string UserDefinedFieldInt52 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldInt53

Userdefined field 01-60 of type integer

Declaration
[TemplateTag("dl53")]
public string UserDefinedFieldInt53 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldInt54

Userdefined field 01-60 of type integer

Declaration
[TemplateTag("dl54")]
public string UserDefinedFieldInt54 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldInt55

Userdefined field 01-60 of type integer

Declaration
[TemplateTag("dl55")]
public string UserDefinedFieldInt55 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldInt56

Userdefined field 01-60 of type integer

Declaration
[TemplateTag("dl56")]
public string UserDefinedFieldInt56 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldInt57

Userdefined field 01-60 of type integer

Declaration
[TemplateTag("dl57")]
public string UserDefinedFieldInt57 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldInt58

Userdefined field 01-60 of type integer

Declaration
[TemplateTag("dl58")]
public string UserDefinedFieldInt58 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldInt59

Userdefined field 01-60 of type integer

Declaration
[TemplateTag("dl59")]
public string UserDefinedFieldInt59 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldInt6

Userdefined field 01-60 of type integer

Declaration
[TemplateTag("dl06")]
public string UserDefinedFieldInt6 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldInt60

Userdefined field 01-60 of type integer

Declaration
[TemplateTag("dl60")]
public string UserDefinedFieldInt60 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldInt7

Userdefined field 01-60 of type integer

Declaration
[TemplateTag("dl07")]
public string UserDefinedFieldInt7 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldInt8

Userdefined field 01-60 of type integer

Declaration
[TemplateTag("dl08")]
public string UserDefinedFieldInt8 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldInt9

Userdefined field 01-60 of type integer

Declaration
[TemplateTag("dl09")]
public string UserDefinedFieldInt9 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldString1

Userdefined field 1 of type string

Declaration
[TemplateTag("ds01")]
public string UserDefinedFieldString1 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldString10

Userdefined field 01-49 of type string

Declaration
[TemplateTag("ds10")]
public string UserDefinedFieldString10 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldString11

Userdefined field 01-49 of type string

Declaration
[TemplateTag("ds11")]
public string UserDefinedFieldString11 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldString12

Userdefined field 01-49 of type string

Declaration
[TemplateTag("ds12")]
public string UserDefinedFieldString12 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldString13

Userdefined field 01-49 of type string

Declaration
[TemplateTag("ds13")]
public string UserDefinedFieldString13 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldString14

Userdefined field 01-49 of type string

Declaration
[TemplateTag("ds14")]
public string UserDefinedFieldString14 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldString15

Userdefined field 01-49 of type string

Declaration
[TemplateTag("ds15")]
public string UserDefinedFieldString15 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldString16

Userdefined field 01-49 of type string

Declaration
[TemplateTag("ds16")]
public string UserDefinedFieldString16 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldString17

Userdefined field 01-49 of type string

Declaration
[TemplateTag("ds17")]
public string UserDefinedFieldString17 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldString18

Userdefined field 01-49 of type string

Declaration
[TemplateTag("ds18")]
public string UserDefinedFieldString18 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldString19

Userdefined field 01-49 of type string

Declaration
[TemplateTag("ds19")]
public string UserDefinedFieldString19 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldString2

Userdefined field 2 of type string

Declaration
[TemplateTag("ds02")]
public string UserDefinedFieldString2 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldString20

Userdefined field 01-49 of type string

Declaration
[TemplateTag("ds20")]
public string UserDefinedFieldString20 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldString21

Userdefined field 01-49 of type string

Declaration
[TemplateTag("ds21")]
public string UserDefinedFieldString21 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldString22

Userdefined field 01-49 of type string

Declaration
[TemplateTag("ds22")]
public string UserDefinedFieldString22 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldString23

Userdefined field 01-49 of type string

Declaration
[TemplateTag("ds23")]
public string UserDefinedFieldString23 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldString24

Userdefined field 01-49 of type string

Declaration
[TemplateTag("ds24")]
public string UserDefinedFieldString24 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldString25

Userdefined field 01-49 of type string

Declaration
[TemplateTag("ds25")]
public string UserDefinedFieldString25 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldString26

Userdefined field 01-49 of type string

Declaration
[TemplateTag("ds26")]
public string UserDefinedFieldString26 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldString27

Userdefined field 01-49 of type string

Declaration
[TemplateTag("ds27")]
public string UserDefinedFieldString27 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldString28

Userdefined field 01-49 of type string

Declaration
[TemplateTag("ds28")]
public string UserDefinedFieldString28 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldString29

Userdefined field 01-49 of type string

Declaration
[TemplateTag("ds29")]
public string UserDefinedFieldString29 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldString3

Userdefined field 01-49 of type string

Declaration
[TemplateTag("ds03")]
public string UserDefinedFieldString3 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldString30

Userdefined field 01-49 of type string

Declaration
[TemplateTag("ds30")]
public string UserDefinedFieldString30 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldString31

Userdefined field 01-49 of type string

Declaration
[TemplateTag("ds31")]
public string UserDefinedFieldString31 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldString32

Userdefined field 01-49 of type string

Declaration
[TemplateTag("ds32")]
public string UserDefinedFieldString32 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldString33

Userdefined field 01-49 of type string

Declaration
[TemplateTag("ds33")]
public string UserDefinedFieldString33 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldString34

Userdefined field 01-49 of type string

Declaration
[TemplateTag("ds34")]
public string UserDefinedFieldString34 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldString35

Userdefined field 01-49 of type string

Declaration
[TemplateTag("ds35")]
public string UserDefinedFieldString35 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldString36

Userdefined field 01-49 of type string

Declaration
[TemplateTag("ds36")]
public string UserDefinedFieldString36 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldString37

Userdefined field 01-49 of type string

Declaration
[TemplateTag("ds37")]
public string UserDefinedFieldString37 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldString38

Userdefined field 01-49 of type string

Declaration
[TemplateTag("ds38")]
public string UserDefinedFieldString38 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldString39

Userdefined field 01-49 of type string

Declaration
[TemplateTag("ds39")]
public string UserDefinedFieldString39 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldString4

Userdefined field 01-49 of type string

Declaration
[TemplateTag("ds04")]
public string UserDefinedFieldString4 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldString40

Userdefined field 01-49 of type string

Declaration
[TemplateTag("ds40")]
public string UserDefinedFieldString40 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldString41

Userdefined field 01-49 of type string

Declaration
[TemplateTag("ds41")]
public string UserDefinedFieldString41 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldString42

Userdefined field 01-49 of type string

Declaration
[TemplateTag("ds42")]
public string UserDefinedFieldString42 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldString43

Userdefined field 01-49 of type string

Declaration
[TemplateTag("ds43")]
public string UserDefinedFieldString43 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldString44

Userdefined field 01-49 of type string

Declaration
[TemplateTag("ds44")]
public string UserDefinedFieldString44 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldString45

Userdefined field 01-49 of type string

Declaration
[TemplateTag("ds45")]
public string UserDefinedFieldString45 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldString46

Userdefined field 01-49 of type string

Declaration
[TemplateTag("ds46")]
public string UserDefinedFieldString46 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldString47

Userdefined field 01-49 of type string

Declaration
[TemplateTag("ds47")]
public string UserDefinedFieldString47 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldString48

Userdefined field 01-49 of type string

Declaration
[TemplateTag("ds48")]
public string UserDefinedFieldString48 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldString49

Userdefined field 01-49 of type string

Declaration
[TemplateTag("ds49")]
public string UserDefinedFieldString49 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldString5

Userdefined field 01-49 of type string

Declaration
[TemplateTag("ds05")]
public string UserDefinedFieldString5 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldString6

Userdefined field 01-49 of type string

Declaration
[TemplateTag("ds06")]
public string UserDefinedFieldString6 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldString7

Userdefined field 01-49 of type string

Declaration
[TemplateTag("ds07")]
public string UserDefinedFieldString7 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldString8

Userdefined field 01-49 of type string

Declaration
[TemplateTag("ds08")]
public string UserDefinedFieldString8 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

UserDefinedFieldString9

Userdefined field 01-49 of type string

Declaration
[TemplateTag("ds09")]
public string UserDefinedFieldString9 { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

YourReference

Your reference

Declaration
[TemplateTag("yref")]
public string YourReference { get; }
Property Value
Type Description
string
Remarks

Note to implementers: Please DO NOT make this class dependent on the database for its fundamental data

  • the design is explicitly constructed to allow multiple implementations of the data-carrying Info interface object, including database-free ones. Querying the database for derived information is generally considered OK, depending on the algorithms in each case.

Extension Methods