While this table does not have a field defined as a primary key, the INTEGRATIONRESOURCEID field should be unique and considered a primary key.
Added in Version 8.1
The INTEGRATIONRESOURCE table maintains a list of resources available for synchronization with an integration. For example, tradingAccounts, contacts, etc.
|
|
While this table does not have a field defined as a primary key, the INTEGRATIONRESOURCEID field should be unique and considered a primary key. |
| Field | Datatype (Length) | Allow Nulls | Indexes | Relationship | Related Table and Field |
|---|---|---|---|---|---|
|
INTEGRATIONRESOURCEID |
STANDARDID |
NOT NULL |
INTEGRATIONRESOURCE_PRIMARY (AK) |
|
|
|
CREATEUSER (FK) |
STANDARDID |
NULLS |
|
(Many) to (One) |
|
|
CREATEDATE |
datetime |
NULLS |
|
|
|
|
MODIFYUSER (FK) |
STANDARDID |
NULLS |
|
(Many) to (One) |
|
|
MODIFYDATE |
datetime |
NULLS |
|
|
|
|
ENABLED |
varchar (1) |
NULLS |
|
|
|
|
RESOURCEKIND |
varchar (64) |
NULLS |
|
|
|
|
SYNCDIRECTION |
varchar (64) |
NULLS |
|
|
|
|
INTEGRATIONID (FK) |
varchar (12) |
NULLS |
INTEGRATIONRESOURCE_INTEGRATION (IE) |
(Many) to (One) |
|
|
ENTITYNAME |
varchar (64) |
NULLS |
|
|
|
|
DEFAULTOWNER |
varchar (32) |
NULLS |
|
|
|