While this table does not have a field defined as a primary key, the DEDUPRESULTID field should be unique and considered a primary key.
Added in version 7.5.4
The DEDEUPRESULT table stores the results as Infor CRM processes a de-duplication job.
|
|
While this table does not have a field defined as a primary key, the DEDUPRESULTID field should be unique and considered a primary key. |
| Field | Datatype (Length) | Allow Nulls | Indexes | Relationship | Related Table and Field |
|---|---|---|---|---|---|
|
DEDUPRESULTID |
char(12) |
NOT NULL |
DEDUPRESULT_PRIMARY (AK) |
|
|
|
DEDUPJOBID (FK) |
char(12) |
NOT NULL |
DEDUPRESULT_DEDUPJOBID (IE) |
(Many) to (One) |
|
|
CREATEUSER (FK) |
char(12) |
NULLS |
|
(Many) to (One) |
|
|
CREATEDATE |
datetime |
NULLS |
|
|
|
|
MODIFYUSER (FK) |
char(12) |
NULLS |
|
(Many) to (One) |
|
|
MODIFYDATE |
datetime |
NULLS |
|
|
|
|
SCORE |
int |
NULLS |
|
|
|
|
RESULTCOUNT |
int |
NULLS |
|
|
|
|
RESULTSTATUS |
varchar(32) |
NULLS |
|
|
|
|
RESULTENTITYID (FK) |
char(12) |
NULLS |
|
(Many) to (One) |
depends on value of RESULTENTITYTYPE. For example, if it equals ACCOUNT, then the related table and field are ACCOUNT.ACCOUNTID |
|
SOURCEENTITYID (FK) |
char(12) |
NULLS |
|
(Many) to (One) |
depends on value of RESULTENTITYTYPE. For example, if it equals ACCOUNT, then the related table and field are ACCOUNT.ACCOUNTID |
|
RESULTDESCRIPTION |
varchar(255) |
NULLS |
|
|
|
|
SOURCENTITYTYPE |
varchar(255) |
NULLS |
|
|
|
|
SOURCEENTITYDESCRIPTION |
varchar(255) |
NULLS |
|
|
|
|
RESULTENTITYDESCRIPTION |
varchar(255) |
NULLS |
|
|
|
|
RESULTENTITYTYPE |
varchar(255) |
NULLS |
|
|
|
|
DATA |
text |
NULLS |
|
|
|
|
RESOLVEDDATE |
datetime |
NULLS |
|
|
|
|
RESOLVEDBY (FK) |
char(12) |
NULLS |
|
(Many) to (One) |
|
|
SOURCEENTITYTYPENAME |
varchar(32) |
NULLS |
|
|
|
|
RESULTENTITYTYPENAME |
varchar(32) |
NULLS |
|
|
|