Class FadTags
Template tag supplier for fad0 - fadq address block variables
Inherited Members
Namespace: SuperOffice.CRM.Globalization
Assembly: SoDataBase.dll
Syntax
public class FadTags : 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.
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 _contactInfo
Field 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 _parentVariables
Field 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.
_personInfo
Template tag supplier for fad0 - fadq address block variables
Declaration
protected IPersonInfo2 _personInfo
Field Value
| Type | Description |
|---|---|
| IPersonInfo2 |
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
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.
Fad1(CancellationToken)
Template tag supplier for fad0 - fadq address block variables
Declaration
[TemplateTag("fad1")]
public Task<string> Fad1(CancellationToken cancellationToken = default)
Parameters
| Type | Name | Description |
|---|---|---|
| CancellationToken | cancellationToken |
Returns
| Type | Description |
|---|---|
| Task<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(CancellationToken)
Template tag supplier for fad0 - fadq address block variables
Declaration
[TemplateTag("fad2")]
public Task<string> Fad2(CancellationToken cancellationToken = default)
Parameters
| Type | Name | Description |
|---|---|---|
| CancellationToken | cancellationToken |
Returns
| Type | Description |
|---|---|
| Task<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(CancellationToken)
Template tag supplier for fad0 - fadq address block variables
Declaration
[TemplateTag("fad3")]
public Task<string> Fad3(CancellationToken cancellationToken = default)
Parameters
| Type | Name | Description |
|---|---|---|
| CancellationToken | cancellationToken |
Returns
| Type | Description |
|---|---|
| Task<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(CancellationToken)
Template tag supplier for fad0 - fadq address block variables
Declaration
[TemplateTag("fad4")]
public Task<string> Fad4(CancellationToken cancellationToken = default)
Parameters
| Type | Name | Description |
|---|---|---|
| CancellationToken | cancellationToken |
Returns
| Type | Description |
|---|---|
| Task<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(CancellationToken)
Template tag supplier for fad0 - fadq address block variables
Declaration
[TemplateTag("fad5")]
public Task<string> Fad5(CancellationToken cancellationToken = default)
Parameters
| Type | Name | Description |
|---|---|---|
| CancellationToken | cancellationToken |
Returns
| Type | Description |
|---|---|
| Task<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(CancellationToken)
Template tag supplier for fad0 - fadq address block variables
Declaration
[TemplateTag("fad6")]
public Task<string> Fad6(CancellationToken cancellationToken = default)
Parameters
| Type | Name | Description |
|---|---|---|
| CancellationToken | cancellationToken |
Returns
| Type | Description |
|---|---|
| Task<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(CancellationToken)
Template tag supplier for fad0 - fadq address block variables
Declaration
[TemplateTag("fad7")]
public Task<string> Fad7(CancellationToken cancellationToken = default)
Parameters
| Type | Name | Description |
|---|---|---|
| CancellationToken | cancellationToken |
Returns
| Type | Description |
|---|---|
| Task<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(CancellationToken)
Template tag supplier for fad0 - fadq address block variables
Declaration
[TemplateTag("fad8")]
public Task<string> Fad8(CancellationToken cancellationToken = default)
Parameters
| Type | Name | Description |
|---|---|---|
| CancellationToken | cancellationToken |
Returns
| Type | Description |
|---|---|
| Task<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(CancellationToken)
Template tag supplier for fad0 - fadq address block variables
Declaration
[TemplateTag("fad9")]
public Task<string> Fad9(CancellationToken cancellationToken = default)
Parameters
| Type | Name | Description |
|---|---|---|
| CancellationToken | cancellationToken |
Returns
| Type | Description |
|---|---|
| Task<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(CancellationToken)
Template tag supplier for fad0 - fadq address block variables
Declaration
[TemplateTag("fada")]
public Task<string> Fada(CancellationToken cancellationToken = default)
Parameters
| Type | Name | Description |
|---|---|---|
| CancellationToken | cancellationToken |
Returns
| Type | Description |
|---|---|
| Task<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(CancellationToken)
Template tag supplier for fad0 - fadq address block variables
Declaration
[TemplateTag("fadb")]
public Task<string> Fadb(CancellationToken cancellationToken = default)
Parameters
| Type | Name | Description |
|---|---|---|
| CancellationToken | cancellationToken |
Returns
| Type | Description |
|---|---|
| Task<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(CancellationToken)
Template tag supplier for fad0 - fadq address block variables
Declaration
[TemplateTag("fadc")]
public Task<string> Fadc(CancellationToken cancellationToken = default)
Parameters
| Type | Name | Description |
|---|---|---|
| CancellationToken | cancellationToken |
Returns
| Type | Description |
|---|---|
| Task<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(CancellationToken)
Template tag supplier for fad0 - fadq address block variables
Declaration
[TemplateTag("fadd")]
public Task<string> Fadd(CancellationToken cancellationToken = default)
Parameters
| Type | Name | Description |
|---|---|---|
| CancellationToken | cancellationToken |
Returns
| Type | Description |
|---|---|
| Task<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(CancellationToken)
Template tag supplier for fad0 - fadq address block variables
Declaration
[TemplateTag("fade")]
public Task<string> Fade(CancellationToken cancellationToken = default)
Parameters
| Type | Name | Description |
|---|---|---|
| CancellationToken | cancellationToken |
Returns
| Type | Description |
|---|---|
| Task<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(CancellationToken)
Template tag supplier for fad0 - fadq address block variables
Declaration
[TemplateTag("fadf")]
public Task<string> Fadf(CancellationToken cancellationToken = default)
Parameters
| Type | Name | Description |
|---|---|---|
| CancellationToken | cancellationToken |
Returns
| Type | Description |
|---|---|
| Task<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(CancellationToken)
Template tag supplier for fad0 - fadq address block variables
Declaration
[TemplateTag("fadg")]
public Task<string> Fadg(CancellationToken cancellationToken = default)
Parameters
| Type | Name | Description |
|---|---|---|
| CancellationToken | cancellationToken |
Returns
| Type | Description |
|---|---|
| Task<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(CancellationToken)
Template tag supplier for fad0 - fadq address block variables
Declaration
[TemplateTag("fadh")]
public Task<string> Fadh(CancellationToken cancellationToken = default)
Parameters
| Type | Name | Description |
|---|---|---|
| CancellationToken | cancellationToken |
Returns
| Type | Description |
|---|---|
| Task<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(CancellationToken)
Template tag supplier for fad0 - fadq address block variables
Declaration
[TemplateTag("fadi")]
public Task<string> Fadi(CancellationToken cancellationToken = default)
Parameters
| Type | Name | Description |
|---|---|---|
| CancellationToken | cancellationToken |
Returns
| Type | Description |
|---|---|
| Task<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(CancellationToken)
Template tag supplier for fad0 - fadq address block variables
Declaration
[TemplateTag("fadj")]
public Task<string> Fadj(CancellationToken cancellationToken = default)
Parameters
| Type | Name | Description |
|---|---|---|
| CancellationToken | cancellationToken |
Returns
| Type | Description |
|---|---|
| Task<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(CancellationToken)
Template tag supplier for fad0 - fadq address block variables
Declaration
[TemplateTag("fadk")]
public Task<string> Fadk(CancellationToken cancellationToken = default)
Parameters
| Type | Name | Description |
|---|---|---|
| CancellationToken | cancellationToken |
Returns
| Type | Description |
|---|---|
| Task<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(CancellationToken)
Template tag supplier for fad0 - fadq address block variables
Declaration
[TemplateTag("fadl")]
public Task<string> Fadl(CancellationToken cancellationToken = default)
Parameters
| Type | Name | Description |
|---|---|---|
| CancellationToken | cancellationToken |
Returns
| Type | Description |
|---|---|
| Task<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(CancellationToken)
Template tag supplier for fad0 - fadq address block variables
Declaration
[TemplateTag("fadm")]
public Task<string> Fadm(CancellationToken cancellationToken = default)
Parameters
| Type | Name | Description |
|---|---|---|
| CancellationToken | cancellationToken |
Returns
| Type | Description |
|---|---|
| Task<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(CancellationToken)
Template tag supplier for fad0 - fadq address block variables
Declaration
[TemplateTag("fadn")]
public Task<string> Fadn(CancellationToken cancellationToken = default)
Parameters
| Type | Name | Description |
|---|---|---|
| CancellationToken | cancellationToken |
Returns
| Type | Description |
|---|---|
| Task<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(CancellationToken)
Template tag supplier for fad0 - fadq address block variables
Declaration
[TemplateTag("fado")]
public Task<string> Fado(CancellationToken cancellationToken = default)
Parameters
| Type | Name | Description |
|---|---|---|
| CancellationToken | cancellationToken |
Returns
| Type | Description |
|---|---|
| Task<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(CancellationToken)
Template tag supplier for fad0 - fadq address block variables
Declaration
[TemplateTag("fadp")]
public Task<string> Fadp(CancellationToken cancellationToken = default)
Parameters
| Type | Name | Description |
|---|---|---|
| CancellationToken | cancellationToken |
Returns
| Type | Description |
|---|---|
| Task<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(CancellationToken)
Template tag supplier for fad0 - fadq address block variables
Declaration
[TemplateTag("fadq")]
public Task<string> Fadq(CancellationToken cancellationToken = default)
Parameters
| Type | Name | Description |
|---|---|---|
| CancellationToken | cancellationToken |
Returns
| Type | Description |
|---|---|
| Task<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.
GenerateFadsAsync(CancellationToken)
Generate the FAD data block by doing a recursive tag substitution followed by parsing of conditional elements
Declaration
protected virtual Task GenerateFadsAsync(CancellationToken cancellationToken = default)
Parameters
| Type | Name | Description |
|---|---|---|
| CancellationToken | cancellationToken |
Returns
| Type | Description |
|---|---|
| Task |
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.
GetIdAsync(CancellationToken)
Primary key of the
Declaration
public override Task<int> GetIdAsync(CancellationToken cancellationToken = default)
Parameters
| Type | Name | Description |
|---|---|---|
| CancellationToken | cancellationToken |
Returns
| Type | Description |
|---|---|
| Task<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.
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.
InitAsync(CancellationToken)
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 Task InitAsync(CancellationToken cancellationToken = default)
Parameters
| Type | Name | Description |
|---|---|---|
| CancellationToken | cancellationToken |
Returns
| Type | Description |
|---|---|
| Task |
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.