Skip to main content

<a id=“SuperOffice_WebApi_Data_Associate”></a> Class Associate

Namespace: SuperOffice.WebApi.Data
Assembly: SuperOffice.WebApi.dll
Carrier object for Associate.

Inheritance

objectCarrierAssociate

Inherited Members

Carrier.TableRight, Carrier.FieldProperties, object.ToString(), object.Equals(object), object.Equals(object, object), object.ReferenceEquals(object, object), object.GetHashCode(), object.GetType(), object.MemberwiseClone()

Examples

Get Associate 123 using the WebApi client: <pre><code class=“lang-csharp”>var configuration = new WebApiConfiguration(url); var agent = new AssociateAgent(configuration); var associate = agent.GetAssociate( 123 );</code></pre>

Constructors

<a id=“SuperOffice_WebApi_Data_Associate__ctor”></a> Associate()

Default constructor - defaults any enum props to 0.

Properties

<a id=“SuperOffice_WebApi_Data_Associate_AssociateId”></a> AssociateId

Primary key

Property Value

int

<a id=“SuperOffice_WebApi_Data_Associate_CustomFields”></a> CustomFields

Udef + Extra fields added to the carrier. Extra fields as defined by changes to database schema + user-defined fields as defined by admin. Custom fields combines user defined fields and extra fields into one bucket. The individual <xref href=“SuperOffice.WebApi.Data.Associate.ExtraFields” data-throw-if-not-resolved=“false”></xref> and UserDefinedFields properties are deprecated in favor of this combined collection. The value string is the encoded value: “[I:123]” or “[DT:2019-09-11]”.

Property Value

StringDictionary

Remarks

The naming convention of the key string is as follows: <table><tbody><tr><td class=“term”>Extra field data</td><td class=“description”> [Extra field name]<p></p> Example: <pre><code class=“lang-csharp”>‘x_gorp’ = ‘[I:123]’</code></pre> </td></tr><tr><td class=“term”>User defined field data</td><td class=“description”> [Prog-id name]<p></p> Example: <pre><code class=“lang-csharp”>‘SuperOffice:1’ = ‘[I:123]’</code></pre><p></p> </td></tr></tbody></table>

<a id=“SuperOffice_WebApi_Data_Associate_Deleted”></a> Deleted

If true, the user is retired and should have no rights, not appear in lists, etc.

Property Value

bool

<a id=“SuperOffice_WebApi_Data_Associate_EjUserId”></a> EjUserId

ID of the ej user record corresponding to this associate; 0 for associates that are not ej users

Property Value

int

<a id=“SuperOffice_WebApi_Data_Associate_ExtraFields”></a> ExtraFields

Deprecated: Use <xref href=“SuperOffice.WebApi.Data.Associate.CustomFields” data-throw-if-not-resolved=“false”></xref> instead. Extra fields added to the carrier. This could be data from Plug-ins, the foreign key system, external applications, etc. The value string is the encoded value: “[I:123]” or “[DT:2019-09-11]”.

Property Value

StringDictionary

Remarks

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

<a id=“SuperOffice_WebApi_Data_Associate_FormalName”></a> FormalName

The associate’s culture formatted formalname (firstname, middleName and lastname, title, mrmrs)

Property Value

string

<a id=“SuperOffice_WebApi_Data_Associate_FullName”></a> FullName

The associate’s culture formatted fullname (firstname, middleName and lastname)

Property Value

string

<a id=“SuperOffice_WebApi_Data_Associate_GroupIdx”></a> GroupIdx

Primary group membership, see UserGroupLink for secondary memberships

Property Value

int

<a id=“SuperOffice_WebApi_Data_Associate_Name”></a> Name

Initials, also login name, possibly database user name

Property Value

string

<a id=“SuperOffice_WebApi_Data_Associate_PersonId”></a> PersonId

Owning person record <p>Use MDO List name “person” to get list items.</p>

Property Value

int

<a id=“SuperOffice_WebApi_Data_Associate_Rank”></a> Rank

Rank order

Property Value

short

<a id=“SuperOffice_WebApi_Data_Associate_Tooltip”></a> Tooltip

Tooltip or other description

Property Value

string

<a id=“SuperOffice_WebApi_Data_Associate_Type”></a> Type

User type - 1 = internal user, 2 = resource, 3 = external user, 4 = anonymous, 5 = system NULL if unknown enum value.

Property Value

UserType?

See Also

Associate.Type_String

<a id=“SuperOffice_WebApi_Data_Associate_Type_String”></a> Type_String

User type - 1 = internal user, 2 = resource, 3 = external user, 4 = anonymous, 5 = system Raw string enum value.

Property Value

string

See Also

Associate.Type

<a id=“SuperOffice_WebApi_Data_Associate_UserName”></a> UserName

User name

Property Value

string

See Also

AssociateAgent