Class SaleTags

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

SaleTags(int)

Substitution tags for a sale, based on data from a ISaleInfo2

Declaration

public SaleTags(int saleId)

Parameters

Type	Name	Description
int	saleId

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

_sale

Variable holding ISaleInfo2, use the Sale property to access this variable.

Declaration

protected ISaleInfo2 _sale

Field Value

Type	Description
ISaleInfo2

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

Amount

Sale amount

Declaration

[TemplateTag("saam")]
public double Amount { get; }

Property Value

Type	Description
double

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.

Associate

Associate Associate that owns the sale - full name

Declaration

[TemplateTag("saau")]
public string Associate { 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.

Cost

Sale cost (Amount - Earning)

Declaration

[TemplateTag("salc")]
public double Cost { get; }

Property Value

Type	Description
double

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.

CreatedASsociateId

Sale Created associate ID

Declaration

[TemplateTag("saci")]
public int CreatedASsociateId { 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.

CreatedAssociate

Sale Created associate - Full name

Declaration

[TemplateTag("saca")]
public string CreatedAssociate { 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.

Currency

Sale currency

Declaration

[TemplateTag("sacu")]
public string Currency { 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.

Earning

Sale earning

Declaration

[TemplateTag("saea")]
public double Earning { get; }

Property Value

Type	Description
double

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.

EarningPercent

Sale earning percent

Declaration

[TemplateTag("saep")]
public double EarningPercent { get; }

Property Value

Type	Description
double

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.

HasStakeholders

Is Stakeholders enabled on this sale. Translated "Yes" or "No".

Declaration

[TemplateTag("sste")]
public string HasStakeholders { 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

Sale ID

Declaration

[TemplateTag("said")]
public override int Id { get; }

Property Value

Type	Description
int

Overrides

TagContainer.Id

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.

InfoText

Sale Info text

Declaration

[TemplateTag("sanf")]
public string InfoText { 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.

IsGuided

Is the sale guided? "Yes" or "No".

Declaration

[TemplateTag("sgui")]
public string IsGuided { 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.

Number

Sale number

Declaration

[TemplateTag("sanu")]
public string Number { 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

Sale active event date

Declaration

[TemplateTag("sapa")]
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

Sale, end date for publishing

Declaration

[TemplateTag("sape")]
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

Sale, start date for publishing

Declaration

[TemplateTag("saps")]
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.

Registered

Sale Registered date

Declaration

[TemplateTag("sarg")]
public string Registered { 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.

Sale

Substitution tags for a sale, based on data from a ISaleInfo2

Declaration

protected ISaleInfo2 Sale { get; }

Property Value

Type	Description
ISaleInfo2

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.

SaleSource

Sale source (List item text)

Declaration

[TemplateTag("saso")]
public string SaleSource { 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.

SaleType

Sale type

Declaration

[TemplateTag("saty")]
public string SaleType { 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.

Salecompetitor

Competitor

Declaration

[TemplateTag("saco")]
public string Salecompetitor { 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.

Salecredited

Credited

Declaration

[TemplateTag("sacr")]
public string Salecredited { 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.

Saledate

Sale date

Declaration

[TemplateTag("sada")]
public string Saledate { 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.

Salenextduedate

Next due date

Declaration

[TemplateTag("sadu")]
public string Salenextduedate { 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.

Saleprobability

Probability

Declaration

[TemplateTag("sapr")]
public short Saleprobability { get; }

Property Value

Type	Description
short

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.

Salereason

Reason for lost, sold or stalled

Declaration

[TemplateTag("sare")]
public string Salereason { 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.

Salestage

Sale stage

Declaration

[TemplateTag("sast")]
public string Salestage { 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.

Salestatus

Sale status

Declaration

[TemplateTag("satu")]
public string Salestatus { 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.

Title

Title of the sale

Declaration

[TemplateTag("sati")]
public string Title { 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("sf01")]
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("sf10")]
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("sf02")]
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("sf03")]
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("sf04")]
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("sf05")]
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("sf06")]
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("sf07")]
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("sf08")]
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("sf09")]
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("sl01")]
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("sl10")]
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("sl11")]
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("sl12")]
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("sl13")]
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("sl14")]
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("sl15")]
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("sl16")]
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("sl17")]
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("sl18")]
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("sl19")]
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("sl02")]
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("sl20")]
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("sl21")]
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("sl22")]
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("sl23")]
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("sl24")]
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("sl25")]
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("sl26")]
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("sl27")]
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("sl28")]
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("sl29")]
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("sl03")]
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("sl30")]
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("sl31")]
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("sl32")]
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("sl33")]
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("sl34")]
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("sl35")]
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("sl36")]
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("sl37")]
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("sl38")]
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("sl39")]
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("sl04")]
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("sl40")]
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("sl41")]
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("sl42")]
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("sl43")]
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("sl44")]
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("sl45")]
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("sl46")]
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("sl47")]
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("sl48")]
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("sl49")]
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("sl05")]
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("sl50")]
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("sl51")]
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("sl52")]
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("sl53")]
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("sl54")]
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("sl55")]
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("sl56")]
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("sl57")]
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("sl58")]
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("sl59")]
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("sl06")]
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("sl60")]
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("sl07")]
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("sl08")]
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("sl09")]
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("ss01")]
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("ss10")]
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("ss11")]
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("ss12")]
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("ss13")]
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("ss14")]
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("ss15")]
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("ss16")]
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("ss17")]
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("ss18")]
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("ss19")]
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("ss02")]
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("ss20")]
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("ss21")]
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("ss22")]
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("ss23")]
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("ss24")]
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("ss25")]
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("ss26")]
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("ss27")]
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("ss28")]
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("ss29")]
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("ss03")]
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("ss30")]
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("ss31")]
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("ss32")]
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("ss33")]
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("ss34")]
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("ss35")]
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("ss36")]
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("ss37")]
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("ss38")]
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("ss39")]
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("ss04")]
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("ss40")]
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("ss41")]
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("ss42")]
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("ss43")]
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("ss44")]
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("ss45")]
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("ss46")]
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("ss47")]
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("ss48")]
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("ss49")]
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("ss05")]
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("ss06")]
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("ss07")]
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("ss08")]
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("ss09")]
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.

Extension Methods

EnumUtil.MapEnums<From, To>(From)

Converters.MapEnums<From, To>(From)