While this table does not have a field defined as a primary key, the IMPORTHISTORYITEMID field should be unique and considered a primary key.
Added in Version 7.5
The IMPORTHISTORYITEM table stores import information, at the record level, during a lead import such as Errors, Warnings and Duplicates
|
|
While this table does not have a field defined as a primary key, the IMPORTHISTORYITEMID field should be unique and considered a primary key. |
| Field | Datatype (Length) | Allow Nulls | Indexes | Relationship | Related Table and Field |
|---|---|---|---|---|---|
|
IMPORTHISTORYITEMID |
char(12) |
NOT NULL |
IMPORTHISTORYITEM_PRIMARY (AK) |
|
|
|
IMPORTHISTORYID (FK) |
char(12) |
NOT NULL |
IMPHISITEM_IMPHISID (IE) |
(Many) to (One) |
|
|
CREATEUSER |
char(12) |
NULLS |
|
(Many) to (One) |
|
|
CREATEDATE |
datetime(8) |
NULLS |
|
|
|
|
MODIFYUSER |
char(12) |
NULLS |
|
(Many) to (One) |
|
|
MODIFYDATE |
datetime(8) |
NULLS |
|
|
|
|
DESCRIPTION |
varchar(255) |
NULLS |
|
|
|
|
ITEMTYPE |
varchar(32) |
NULLS |
|
|
|
|
NOTE |
text(16) |
NULLS |
|
|
|
|
DATA |
text(16) |
NULLS |
|
|
|
|
ISRESOLVED |
varchar(1) |
NULLS |
|
|
|
|
RESOLVEDDATE |
datetime(8) |
NULLS |
|
|
|
|
RESOLVEDREFERENCEID |
char(12) |
NULLS |
|
|
|
|
RESOLVEENTITYTYPE |
varchar(32) |
NULLS |
|
|
|
|
RESOLVEDESCRIPTION |
varchar(255) |
NULLS |
|
|
|