Class FadTags
Template tag supplier for fad0 - fadq address block variables
Inherited Members
Namespace: SuperOffice.CRM.Globalization
Assembly: SoDataBase.dll
Syntax
public class FadTags : TagContainerRemarks
The fad variables are formatted according to format strings that refer to other template variables, as well as containing a special syntax for inserting conditional or hard spaces, line feeds and other formatting.
Format strings reside in the addressformat table. Which one is used depends on the home country of the sender and the country of the receiver, and whether a person or company address is used.Note that according to the C++ code we seek to imitate, it's the database owner contact.country_id that is the 'sender', and not the current principal (which you might think more logical, but tell that to the C++ code... in rdb/AddressFormatManager.cpp line 231). The formatting code is directly converted from the C++ version with minimal changes. The C++ functionality for retrieving ONLY the address part (and not the name) is not implemented, as it is used only from Reporter.
Constructors
FadTags(IPersonInfo2, IContactInfo2, TagContainer)
Construct the class, decide which format to use, and generate the data for all the lines
Declaration
public FadTags(IPersonInfo2 personInfo, IContactInfo2 contactInfo, TagContainer parent)Parameters
| Type | Name | Description |
|---|---|---|
| IPersonInfo2 | personInfo | Person information to use |
| IContactInfo2 | contactInfo | Contact information to use |
| TagContainer | parent | Parent, used to get hold of inner tag values |
Remarks
The fad variables are formatted according to format strings that refer to other template variables, as well as containing a special syntax for inserting conditional or hard spaces, line feeds and other formatting.
Format strings reside in the addressformat table. Which one is used depends on the home country of the sender and the country of the receiver, and whether a person or company address is used.Note that according to the C++ code we seek to imitate, it's the database owner contact.country_id that is the 'sender', and not the current principal (which you might think more logical, but tell that to the C++ code... in rdb/AddressFormatManager.cpp line 231). The formatting code is directly converted from the C++ version with minimal changes. The C++ functionality for retrieving ONLY the address part (and not the name) is not implemented, as it is used only from Reporter.
Fields
_contactInfo
Template tag supplier for fad0 - fadq address block variables
Declaration
protected IContactInfo2 _contactInfoField Value
| Type | Description |
|---|---|
| IContactInfo2 |
Remarks
The fad variables are formatted according to format strings that refer to other template variables, as well as containing a special syntax for inserting conditional or hard spaces, line feeds and other formatting.
Format strings reside in the addressformat table. Which one is used depends on the home country of the sender and the country of the receiver, and whether a person or company address is used.Note that according to the C++ code we seek to imitate, it's the database owner contact.country_id that is the 'sender', and not the current principal (which you might think more logical, but tell that to the C++ code... in rdb/AddressFormatManager.cpp line 231). The formatting code is directly converted from the C++ version with minimal changes. The C++ functionality for retrieving ONLY the address part (and not the name) is not implemented, as it is used only from Reporter.
_parentVariables
Template tag supplier for fad0 - fadq address block variables
Declaration
protected TagContainer _parentVariablesField Value
| Type | Description |
|---|---|
| TagContainer |
Remarks
The fad variables are formatted according to format strings that refer to other template variables, as well as containing a special syntax for inserting conditional or hard spaces, line feeds and other formatting.
Format strings reside in the addressformat table. Which one is used depends on the home country of the sender and the country of the receiver, and whether a person or company address is used.Note that according to the C++ code we seek to imitate, it's the database owner contact.country_id that is the 'sender', and not the current principal (which you might think more logical, but tell that to the C++ code... in rdb/AddressFormatManager.cpp line 231). The formatting code is directly converted from the C++ version with minimal changes. The C++ functionality for retrieving ONLY the address part (and not the name) is not implemented, as it is used only from Reporter.
Properties
Fad1
Template tag supplier for fad0 - fadq address block variables
Declaration
[TemplateTag("fad1")]
public string Fad1 { get; }Property Value
| Type | Description |
|---|---|
| string |
Remarks
The fad variables are formatted according to format strings that refer to other template variables, as well as containing a special syntax for inserting conditional or hard spaces, line feeds and other formatting.
Format strings reside in the addressformat table. Which one is used depends on the home country of the sender and the country of the receiver, and whether a person or company address is used.Note that according to the C++ code we seek to imitate, it's the database owner contact.country_id that is the 'sender', and not the current principal (which you might think more logical, but tell that to the C++ code... in rdb/AddressFormatManager.cpp line 231). The formatting code is directly converted from the C++ version with minimal changes. The C++ functionality for retrieving ONLY the address part (and not the name) is not implemented, as it is used only from Reporter.
Fad2
Template tag supplier for fad0 - fadq address block variables
Declaration
[TemplateTag("fad2")]
public string Fad2 { get; }Property Value
| Type | Description |
|---|---|
| string |
Remarks
The fad variables are formatted according to format strings that refer to other template variables, as well as containing a special syntax for inserting conditional or hard spaces, line feeds and other formatting.
Format strings reside in the addressformat table. Which one is used depends on the home country of the sender and the country of the receiver, and whether a person or company address is used.Note that according to the C++ code we seek to imitate, it's the database owner contact.country_id that is the 'sender', and not the current principal (which you might think more logical, but tell that to the C++ code... in rdb/AddressFormatManager.cpp line 231). The formatting code is directly converted from the C++ version with minimal changes. The C++ functionality for retrieving ONLY the address part (and not the name) is not implemented, as it is used only from Reporter.
Fad3
Template tag supplier for fad0 - fadq address block variables
Declaration
[TemplateTag("fad3")]
public string Fad3 { get; }Property Value
| Type | Description |
|---|---|
| string |
Remarks
The fad variables are formatted according to format strings that refer to other template variables, as well as containing a special syntax for inserting conditional or hard spaces, line feeds and other formatting.
Format strings reside in the addressformat table. Which one is used depends on the home country of the sender and the country of the receiver, and whether a person or company address is used.Note that according to the C++ code we seek to imitate, it's the database owner contact.country_id that is the 'sender', and not the current principal (which you might think more logical, but tell that to the C++ code... in rdb/AddressFormatManager.cpp line 231). The formatting code is directly converted from the C++ version with minimal changes. The C++ functionality for retrieving ONLY the address part (and not the name) is not implemented, as it is used only from Reporter.
Fad4
Template tag supplier for fad0 - fadq address block variables
Declaration
[TemplateTag("fad4")]
public string Fad4 { get; }Property Value
| Type | Description |
|---|---|
| string |
Remarks
The fad variables are formatted according to format strings that refer to other template variables, as well as containing a special syntax for inserting conditional or hard spaces, line feeds and other formatting.
Format strings reside in the addressformat table. Which one is used depends on the home country of the sender and the country of the receiver, and whether a person or company address is used.Note that according to the C++ code we seek to imitate, it's the database owner contact.country_id that is the 'sender', and not the current principal (which you might think more logical, but tell that to the C++ code... in rdb/AddressFormatManager.cpp line 231). The formatting code is directly converted from the C++ version with minimal changes. The C++ functionality for retrieving ONLY the address part (and not the name) is not implemented, as it is used only from Reporter.
Fad5
Template tag supplier for fad0 - fadq address block variables
Declaration
[TemplateTag("fad5")]
public string Fad5 { get; }Property Value
| Type | Description |
|---|---|
| string |
Remarks
The fad variables are formatted according to format strings that refer to other template variables, as well as containing a special syntax for inserting conditional or hard spaces, line feeds and other formatting.
Format strings reside in the addressformat table. Which one is used depends on the home country of the sender and the country of the receiver, and whether a person or company address is used.Note that according to the C++ code we seek to imitate, it's the database owner contact.country_id that is the 'sender', and not the current principal (which you might think more logical, but tell that to the C++ code... in rdb/AddressFormatManager.cpp line 231). The formatting code is directly converted from the C++ version with minimal changes. The C++ functionality for retrieving ONLY the address part (and not the name) is not implemented, as it is used only from Reporter.
Fad6
Template tag supplier for fad0 - fadq address block variables
Declaration
[TemplateTag("fad6")]
public string Fad6 { get; }Property Value
| Type | Description |
|---|---|
| string |
Remarks
The fad variables are formatted according to format strings that refer to other template variables, as well as containing a special syntax for inserting conditional or hard spaces, line feeds and other formatting.
Format strings reside in the addressformat table. Which one is used depends on the home country of the sender and the country of the receiver, and whether a person or company address is used.Note that according to the C++ code we seek to imitate, it's the database owner contact.country_id that is the 'sender', and not the current principal (which you might think more logical, but tell that to the C++ code... in rdb/AddressFormatManager.cpp line 231). The formatting code is directly converted from the C++ version with minimal changes. The C++ functionality for retrieving ONLY the address part (and not the name) is not implemented, as it is used only from Reporter.
Fad7
Template tag supplier for fad0 - fadq address block variables
Declaration
[TemplateTag("fad7")]
public string Fad7 { get; }Property Value
| Type | Description |
|---|---|
| string |
Remarks
The fad variables are formatted according to format strings that refer to other template variables, as well as containing a special syntax for inserting conditional or hard spaces, line feeds and other formatting.
Format strings reside in the addressformat table. Which one is used depends on the home country of the sender and the country of the receiver, and whether a person or company address is used.Note that according to the C++ code we seek to imitate, it's the database owner contact.country_id that is the 'sender', and not the current principal (which you might think more logical, but tell that to the C++ code... in rdb/AddressFormatManager.cpp line 231). The formatting code is directly converted from the C++ version with minimal changes. The C++ functionality for retrieving ONLY the address part (and not the name) is not implemented, as it is used only from Reporter.
Fad8
Template tag supplier for fad0 - fadq address block variables
Declaration
[TemplateTag("fad8")]
public string Fad8 { get; }Property Value
| Type | Description |
|---|---|
| string |
Remarks
The fad variables are formatted according to format strings that refer to other template variables, as well as containing a special syntax for inserting conditional or hard spaces, line feeds and other formatting.
Format strings reside in the addressformat table. Which one is used depends on the home country of the sender and the country of the receiver, and whether a person or company address is used.Note that according to the C++ code we seek to imitate, it's the database owner contact.country_id that is the 'sender', and not the current principal (which you might think more logical, but tell that to the C++ code... in rdb/AddressFormatManager.cpp line 231). The formatting code is directly converted from the C++ version with minimal changes. The C++ functionality for retrieving ONLY the address part (and not the name) is not implemented, as it is used only from Reporter.
Fad9
Template tag supplier for fad0 - fadq address block variables
Declaration
[TemplateTag("fad9")]
public string Fad9 { get; }Property Value
| Type | Description |
|---|---|
| string |
Remarks
The fad variables are formatted according to format strings that refer to other template variables, as well as containing a special syntax for inserting conditional or hard spaces, line feeds and other formatting.
Format strings reside in the addressformat table. Which one is used depends on the home country of the sender and the country of the receiver, and whether a person or company address is used.Note that according to the C++ code we seek to imitate, it's the database owner contact.country_id that is the 'sender', and not the current principal (which you might think more logical, but tell that to the C++ code... in rdb/AddressFormatManager.cpp line 231). The formatting code is directly converted from the C++ version with minimal changes. The C++ functionality for retrieving ONLY the address part (and not the name) is not implemented, as it is used only from Reporter.
Fada
Template tag supplier for fad0 - fadq address block variables
Declaration
[TemplateTag("fada")]
public string Fada { get; }Property Value
| Type | Description |
|---|---|
| string |
Remarks
The fad variables are formatted according to format strings that refer to other template variables, as well as containing a special syntax for inserting conditional or hard spaces, line feeds and other formatting.
Format strings reside in the addressformat table. Which one is used depends on the home country of the sender and the country of the receiver, and whether a person or company address is used.Note that according to the C++ code we seek to imitate, it's the database owner contact.country_id that is the 'sender', and not the current principal (which you might think more logical, but tell that to the C++ code... in rdb/AddressFormatManager.cpp line 231). The formatting code is directly converted from the C++ version with minimal changes. The C++ functionality for retrieving ONLY the address part (and not the name) is not implemented, as it is used only from Reporter.
Fadb
Template tag supplier for fad0 - fadq address block variables
Declaration
[TemplateTag("fadb")]
public string Fadb { get; }Property Value
| Type | Description |
|---|---|
| string |
Remarks
The fad variables are formatted according to format strings that refer to other template variables, as well as containing a special syntax for inserting conditional or hard spaces, line feeds and other formatting.
Format strings reside in the addressformat table. Which one is used depends on the home country of the sender and the country of the receiver, and whether a person or company address is used.Note that according to the C++ code we seek to imitate, it's the database owner contact.country_id that is the 'sender', and not the current principal (which you might think more logical, but tell that to the C++ code... in rdb/AddressFormatManager.cpp line 231). The formatting code is directly converted from the C++ version with minimal changes. The C++ functionality for retrieving ONLY the address part (and not the name) is not implemented, as it is used only from Reporter.
Fadc
Template tag supplier for fad0 - fadq address block variables
Declaration
[TemplateTag("fadc")]
public string Fadc { get; }Property Value
| Type | Description |
|---|---|
| string |
Remarks
The fad variables are formatted according to format strings that refer to other template variables, as well as containing a special syntax for inserting conditional or hard spaces, line feeds and other formatting.
Format strings reside in the addressformat table. Which one is used depends on the home country of the sender and the country of the receiver, and whether a person or company address is used.Note that according to the C++ code we seek to imitate, it's the database owner contact.country_id that is the 'sender', and not the current principal (which you might think more logical, but tell that to the C++ code... in rdb/AddressFormatManager.cpp line 231). The formatting code is directly converted from the C++ version with minimal changes. The C++ functionality for retrieving ONLY the address part (and not the name) is not implemented, as it is used only from Reporter.
Fadd
Template tag supplier for fad0 - fadq address block variables
Declaration
[TemplateTag("fadd")]
public string Fadd { get; }Property Value
| Type | Description |
|---|---|
| string |
Remarks
The fad variables are formatted according to format strings that refer to other template variables, as well as containing a special syntax for inserting conditional or hard spaces, line feeds and other formatting.
Format strings reside in the addressformat table. Which one is used depends on the home country of the sender and the country of the receiver, and whether a person or company address is used.Note that according to the C++ code we seek to imitate, it's the database owner contact.country_id that is the 'sender', and not the current principal (which you might think more logical, but tell that to the C++ code... in rdb/AddressFormatManager.cpp line 231). The formatting code is directly converted from the C++ version with minimal changes. The C++ functionality for retrieving ONLY the address part (and not the name) is not implemented, as it is used only from Reporter.
Fade
Template tag supplier for fad0 - fadq address block variables
Declaration
[TemplateTag("fade")]
public string Fade { get; }Property Value
| Type | Description |
|---|---|
| string |
Remarks
The fad variables are formatted according to format strings that refer to other template variables, as well as containing a special syntax for inserting conditional or hard spaces, line feeds and other formatting.
Format strings reside in the addressformat table. Which one is used depends on the home country of the sender and the country of the receiver, and whether a person or company address is used.Note that according to the C++ code we seek to imitate, it's the database owner contact.country_id that is the 'sender', and not the current principal (which you might think more logical, but tell that to the C++ code... in rdb/AddressFormatManager.cpp line 231). The formatting code is directly converted from the C++ version with minimal changes. The C++ functionality for retrieving ONLY the address part (and not the name) is not implemented, as it is used only from Reporter.
Fadf
Template tag supplier for fad0 - fadq address block variables
Declaration
[TemplateTag("fadf")]
public string Fadf { get; }Property Value
| Type | Description |
|---|---|
| string |
Remarks
The fad variables are formatted according to format strings that refer to other template variables, as well as containing a special syntax for inserting conditional or hard spaces, line feeds and other formatting.
Format strings reside in the addressformat table. Which one is used depends on the home country of the sender and the country of the receiver, and whether a person or company address is used.Note that according to the C++ code we seek to imitate, it's the database owner contact.country_id that is the 'sender', and not the current principal (which you might think more logical, but tell that to the C++ code... in rdb/AddressFormatManager.cpp line 231). The formatting code is directly converted from the C++ version with minimal changes. The C++ functionality for retrieving ONLY the address part (and not the name) is not implemented, as it is used only from Reporter.
Fadg
Template tag supplier for fad0 - fadq address block variables
Declaration
[TemplateTag("fadg")]
public string Fadg { get; }Property Value
| Type | Description |
|---|---|
| string |
Remarks
The fad variables are formatted according to format strings that refer to other template variables, as well as containing a special syntax for inserting conditional or hard spaces, line feeds and other formatting.
Format strings reside in the addressformat table. Which one is used depends on the home country of the sender and the country of the receiver, and whether a person or company address is used.Note that according to the C++ code we seek to imitate, it's the database owner contact.country_id that is the 'sender', and not the current principal (which you might think more logical, but tell that to the C++ code... in rdb/AddressFormatManager.cpp line 231). The formatting code is directly converted from the C++ version with minimal changes. The C++ functionality for retrieving ONLY the address part (and not the name) is not implemented, as it is used only from Reporter.
Fadh
Template tag supplier for fad0 - fadq address block variables
Declaration
[TemplateTag("fadh")]
public string Fadh { get; }Property Value
| Type | Description |
|---|---|
| string |
Remarks
The fad variables are formatted according to format strings that refer to other template variables, as well as containing a special syntax for inserting conditional or hard spaces, line feeds and other formatting.
Format strings reside in the addressformat table. Which one is used depends on the home country of the sender and the country of the receiver, and whether a person or company address is used.Note that according to the C++ code we seek to imitate, it's the database owner contact.country_id that is the 'sender', and not the current principal (which you might think more logical, but tell that to the C++ code... in rdb/AddressFormatManager.cpp line 231). The formatting code is directly converted from the C++ version with minimal changes. The C++ functionality for retrieving ONLY the address part (and not the name) is not implemented, as it is used only from Reporter.
Fadi
Template tag supplier for fad0 - fadq address block variables
Declaration
[TemplateTag("fadi")]
public string Fadi { get; }Property Value
| Type | Description |
|---|---|
| string |
Remarks
The fad variables are formatted according to format strings that refer to other template variables, as well as containing a special syntax for inserting conditional or hard spaces, line feeds and other formatting.
Format strings reside in the addressformat table. Which one is used depends on the home country of the sender and the country of the receiver, and whether a person or company address is used.Note that according to the C++ code we seek to imitate, it's the database owner contact.country_id that is the 'sender', and not the current principal (which you might think more logical, but tell that to the C++ code... in rdb/AddressFormatManager.cpp line 231). The formatting code is directly converted from the C++ version with minimal changes. The C++ functionality for retrieving ONLY the address part (and not the name) is not implemented, as it is used only from Reporter.
Fadj
Template tag supplier for fad0 - fadq address block variables
Declaration
[TemplateTag("fadj")]
public string Fadj { get; }Property Value
| Type | Description |
|---|---|
| string |
Remarks
The fad variables are formatted according to format strings that refer to other template variables, as well as containing a special syntax for inserting conditional or hard spaces, line feeds and other formatting.
Format strings reside in the addressformat table. Which one is used depends on the home country of the sender and the country of the receiver, and whether a person or company address is used.Note that according to the C++ code we seek to imitate, it's the database owner contact.country_id that is the 'sender', and not the current principal (which you might think more logical, but tell that to the C++ code... in rdb/AddressFormatManager.cpp line 231). The formatting code is directly converted from the C++ version with minimal changes. The C++ functionality for retrieving ONLY the address part (and not the name) is not implemented, as it is used only from Reporter.
Fadk
Template tag supplier for fad0 - fadq address block variables
Declaration
[TemplateTag("fadk")]
public string Fadk { get; }Property Value
| Type | Description |
|---|---|
| string |
Remarks
The fad variables are formatted according to format strings that refer to other template variables, as well as containing a special syntax for inserting conditional or hard spaces, line feeds and other formatting.
Format strings reside in the addressformat table. Which one is used depends on the home country of the sender and the country of the receiver, and whether a person or company address is used.Note that according to the C++ code we seek to imitate, it's the database owner contact.country_id that is the 'sender', and not the current principal (which you might think more logical, but tell that to the C++ code... in rdb/AddressFormatManager.cpp line 231). The formatting code is directly converted from the C++ version with minimal changes. The C++ functionality for retrieving ONLY the address part (and not the name) is not implemented, as it is used only from Reporter.
Fadl
Template tag supplier for fad0 - fadq address block variables
Declaration
[TemplateTag("fadl")]
public string Fadl { get; }Property Value
| Type | Description |
|---|---|
| string |
Remarks
The fad variables are formatted according to format strings that refer to other template variables, as well as containing a special syntax for inserting conditional or hard spaces, line feeds and other formatting.
Format strings reside in the addressformat table. Which one is used depends on the home country of the sender and the country of the receiver, and whether a person or company address is used.Note that according to the C++ code we seek to imitate, it's the database owner contact.country_id that is the 'sender', and not the current principal (which you might think more logical, but tell that to the C++ code... in rdb/AddressFormatManager.cpp line 231). The formatting code is directly converted from the C++ version with minimal changes. The C++ functionality for retrieving ONLY the address part (and not the name) is not implemented, as it is used only from Reporter.
Fadm
Template tag supplier for fad0 - fadq address block variables
Declaration
[TemplateTag("fadm")]
public string Fadm { get; }Property Value
| Type | Description |
|---|---|
| string |
Remarks
The fad variables are formatted according to format strings that refer to other template variables, as well as containing a special syntax for inserting conditional or hard spaces, line feeds and other formatting.
Format strings reside in the addressformat table. Which one is used depends on the home country of the sender and the country of the receiver, and whether a person or company address is used.Note that according to the C++ code we seek to imitate, it's the database owner contact.country_id that is the 'sender', and not the current principal (which you might think more logical, but tell that to the C++ code... in rdb/AddressFormatManager.cpp line 231). The formatting code is directly converted from the C++ version with minimal changes. The C++ functionality for retrieving ONLY the address part (and not the name) is not implemented, as it is used only from Reporter.
Fadn
Template tag supplier for fad0 - fadq address block variables
Declaration
[TemplateTag("fadn")]
public string Fadn { get; }Property Value
| Type | Description |
|---|---|
| string |
Remarks
The fad variables are formatted according to format strings that refer to other template variables, as well as containing a special syntax for inserting conditional or hard spaces, line feeds and other formatting.
Format strings reside in the addressformat table. Which one is used depends on the home country of the sender and the country of the receiver, and whether a person or company address is used.Note that according to the C++ code we seek to imitate, it's the database owner contact.country_id that is the 'sender', and not the current principal (which you might think more logical, but tell that to the C++ code... in rdb/AddressFormatManager.cpp line 231). The formatting code is directly converted from the C++ version with minimal changes. The C++ functionality for retrieving ONLY the address part (and not the name) is not implemented, as it is used only from Reporter.
Fado
Template tag supplier for fad0 - fadq address block variables
Declaration
[TemplateTag("fado")]
public string Fado { get; }Property Value
| Type | Description |
|---|---|
| string |
Remarks
The fad variables are formatted according to format strings that refer to other template variables, as well as containing a special syntax for inserting conditional or hard spaces, line feeds and other formatting.
Format strings reside in the addressformat table. Which one is used depends on the home country of the sender and the country of the receiver, and whether a person or company address is used.Note that according to the C++ code we seek to imitate, it's the database owner contact.country_id that is the 'sender', and not the current principal (which you might think more logical, but tell that to the C++ code... in rdb/AddressFormatManager.cpp line 231). The formatting code is directly converted from the C++ version with minimal changes. The C++ functionality for retrieving ONLY the address part (and not the name) is not implemented, as it is used only from Reporter.
Fadp
Template tag supplier for fad0 - fadq address block variables
Declaration
[TemplateTag("fadp")]
public string Fadp { get; }Property Value
| Type | Description |
|---|---|
| string |
Remarks
The fad variables are formatted according to format strings that refer to other template variables, as well as containing a special syntax for inserting conditional or hard spaces, line feeds and other formatting.
Format strings reside in the addressformat table. Which one is used depends on the home country of the sender and the country of the receiver, and whether a person or company address is used.Note that according to the C++ code we seek to imitate, it's the database owner contact.country_id that is the 'sender', and not the current principal (which you might think more logical, but tell that to the C++ code... in rdb/AddressFormatManager.cpp line 231). The formatting code is directly converted from the C++ version with minimal changes. The C++ functionality for retrieving ONLY the address part (and not the name) is not implemented, as it is used only from Reporter.
Fadq
Template tag supplier for fad0 - fadq address block variables
Declaration
[TemplateTag("fadq")]
public string Fadq { get; }Property Value
| Type | Description |
|---|---|
| string |
Remarks
The fad variables are formatted according to format strings that refer to other template variables, as well as containing a special syntax for inserting conditional or hard spaces, line feeds and other formatting.
Format strings reside in the addressformat table. Which one is used depends on the home country of the sender and the country of the receiver, and whether a person or company address is used.Note that according to the C++ code we seek to imitate, it's the database owner contact.country_id that is the 'sender', and not the current principal (which you might think more logical, but tell that to the C++ code... in rdb/AddressFormatManager.cpp line 231). The formatting code is directly converted from the C++ version with minimal changes. The C++ functionality for retrieving ONLY the address part (and not the name) is not implemented, as it is used only from Reporter.
Id
Primary key of the
Declaration
public override int Id { get; }Property Value
| Type | Description |
|---|---|
| int |
Overrides
Remarks
The fad variables are formatted according to format strings that refer to other template variables, as well as containing a special syntax for inserting conditional or hard spaces, line feeds and other formatting.
Format strings reside in the addressformat table. Which one is used depends on the home country of the sender and the country of the receiver, and whether a person or company address is used.Note that according to the C++ code we seek to imitate, it's the database owner contact.country_id that is the 'sender', and not the current principal (which you might think more logical, but tell that to the C++ code... in rdb/AddressFormatManager.cpp line 231). The formatting code is directly converted from the C++ version with minimal changes. The C++ functionality for retrieving ONLY the address part (and not the name) is not implemented, as it is used only from Reporter.
IsValid
Template tag supplier for fad0 - fadq address block variables
Declaration
protected virtual bool IsValid { get; }Property Value
| Type | Description |
|---|---|
| bool |
Remarks
The fad variables are formatted according to format strings that refer to other template variables, as well as containing a special syntax for inserting conditional or hard spaces, line feeds and other formatting.
Format strings reside in the addressformat table. Which one is used depends on the home country of the sender and the country of the receiver, and whether a person or company address is used.Note that according to the C++ code we seek to imitate, it's the database owner contact.country_id that is the 'sender', and not the current principal (which you might think more logical, but tell that to the C++ code... in rdb/AddressFormatManager.cpp line 231). The formatting code is directly converted from the C++ version with minimal changes. The C++ functionality for retrieving ONLY the address part (and not the name) is not implemented, as it is used only from Reporter.
Methods
DetermineFormat()
Analyze the given person and contact data to determine which address format we should use
Declaration
protected virtual void DetermineFormat()Remarks
The fad variables are formatted according to format strings that refer to other template variables, as well as containing a special syntax for inserting conditional or hard spaces, line feeds and other formatting.
Format strings reside in the addressformat table. Which one is used depends on the home country of the sender and the country of the receiver, and whether a person or company address is used.Note that according to the C++ code we seek to imitate, it's the database owner contact.country_id that is the 'sender', and not the current principal (which you might think more logical, but tell that to the C++ code... in rdb/AddressFormatManager.cpp line 231). The formatting code is directly converted from the C++ version with minimal changes. The C++ functionality for retrieving ONLY the address part (and not the name) is not implemented, as it is used only from Reporter.
GenerateFads()
Generate the FAD data block by doing a recursive tag substitution followed by parsing of conditional elements
Declaration
protected virtual void GenerateFads()Remarks
The fad variables are formatted according to format strings that refer to other template variables, as well as containing a special syntax for inserting conditional or hard spaces, line feeds and other formatting.
Format strings reside in the addressformat table. Which one is used depends on the home country of the sender and the country of the receiver, and whether a person or company address is used.Note that according to the C++ code we seek to imitate, it's the database owner contact.country_id that is the 'sender', and not the current principal (which you might think more logical, but tell that to the C++ code... in rdb/AddressFormatManager.cpp line 231). The formatting code is directly converted from the C++ version with minimal changes. The C++ functionality for retrieving ONLY the address part (and not the name) is not implemented, as it is used only from Reporter.
GetAddressLayout(int)
Template tag supplier for fad0 - fadq address block variables
Declaration
protected virtual AddressLayout GetAddressLayout(int addressType)Parameters
| Type | Name | Description |
|---|---|---|
| int | addressType |
Returns
| Type | Description |
|---|---|
| AddressLayout |
Remarks
The fad variables are formatted according to format strings that refer to other template variables, as well as containing a special syntax for inserting conditional or hard spaces, line feeds and other formatting.
Format strings reside in the addressformat table. Which one is used depends on the home country of the sender and the country of the receiver, and whether a person or company address is used.Note that according to the C++ code we seek to imitate, it's the database owner contact.country_id that is the 'sender', and not the current principal (which you might think more logical, but tell that to the C++ code... in rdb/AddressFormatManager.cpp line 231). The formatting code is directly converted from the C++ version with minimal changes. The C++ functionality for retrieving ONLY the address part (and not the name) is not implemented, as it is used only from Reporter.
GetAddressType()
Template tag supplier for fad0 - fadq address block variables
Declaration
protected virtual int GetAddressType()Returns
| Type | Description |
|---|---|
| int |
Remarks
The fad variables are formatted according to format strings that refer to other template variables, as well as containing a special syntax for inserting conditional or hard spaces, line feeds and other formatting.
Format strings reside in the addressformat table. Which one is used depends on the home country of the sender and the country of the receiver, and whether a person or company address is used.Note that according to the C++ code we seek to imitate, it's the database owner contact.country_id that is the 'sender', and not the current principal (which you might think more logical, but tell that to the C++ code... in rdb/AddressFormatManager.cpp line 231). The formatting code is directly converted from the C++ version with minimal changes. The C++ functionality for retrieving ONLY the address part (and not the name) is not implemented, as it is used only from Reporter.
GetRecipientCountryId(int)
Template tag supplier for fad0 - fadq address block variables
Declaration
protected virtual int GetRecipientCountryId(int addressType)Parameters
| Type | Name | Description |
|---|---|---|
| int | addressType |
Returns
| Type | Description |
|---|---|
| int |
Remarks
The fad variables are formatted according to format strings that refer to other template variables, as well as containing a special syntax for inserting conditional or hard spaces, line feeds and other formatting.
Format strings reside in the addressformat table. Which one is used depends on the home country of the sender and the country of the receiver, and whether a person or company address is used.Note that according to the C++ code we seek to imitate, it's the database owner contact.country_id that is the 'sender', and not the current principal (which you might think more logical, but tell that to the C++ code... in rdb/AddressFormatManager.cpp line 231). The formatting code is directly converted from the C++ version with minimal changes. The C++ functionality for retrieving ONLY the address part (and not the name) is not implemented, as it is used only from Reporter.
Init()
Set the object in an initaited state. This means that no data can be added (e.g. AddData(params object[])) beyound this point.
Declaration
protected override void Init()Overrides
Remarks
The fad variables are formatted according to format strings that refer to other template variables, as well as containing a special syntax for inserting conditional or hard spaces, line feeds and other formatting.
Format strings reside in the addressformat table. Which one is used depends on the home country of the sender and the country of the receiver, and whether a person or company address is used.Note that according to the C++ code we seek to imitate, it's the database owner contact.country_id that is the 'sender', and not the current principal (which you might think more logical, but tell that to the C++ code... in rdb/AddressFormatManager.cpp line 231). The formatting code is directly converted from the C++ version with minimal changes. The C++ functionality for retrieving ONLY the address part (and not the name) is not implemented, as it is used only from Reporter.
UseForeign(int)
Template tag supplier for fad0 - fadq address block variables
Declaration
protected virtual bool UseForeign(int addressType)Parameters
| Type | Name | Description |
|---|---|---|
| int | addressType |
Returns
| Type | Description |
|---|---|
| bool |
Remarks
The fad variables are formatted according to format strings that refer to other template variables, as well as containing a special syntax for inserting conditional or hard spaces, line feeds and other formatting.
Format strings reside in the addressformat table. Which one is used depends on the home country of the sender and the country of the receiver, and whether a person or company address is used.Note that according to the C++ code we seek to imitate, it's the database owner contact.country_id that is the 'sender', and not the current principal (which you might think more logical, but tell that to the C++ code... in rdb/AddressFormatManager.cpp line 231). The formatting code is directly converted from the C++ version with minimal changes. The C++ functionality for retrieving ONLY the address part (and not the name) is not implemented, as it is used only from Reporter.