Difference between revisions of "Records Ignored During an Import"
From LongJump Support Wiki
imported>Aeric |
imported>Aeric |
||
| (3 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
During an import, some incoming records may be ignored. (In general, | During an import, some incoming records may be ignored. (In general, | ||
you'll want to be sure that | you'll want to be sure that the number of ignored records reported in | ||
the [[Import Queue]] matches the number you expect.) | the [[Import Queue#Import Log|Import Log]] matches the number you expect.) | ||
Incoming records are ignored in the following circumstances: | Incoming records are ignored in the following circumstances: | ||
:* The object has a [[Unique Key]], and the new record would cause a | :* The object has a [[Unique Key Index]], and the new record would cause a duplicate key. | ||
:* The <tt>record_id</tt> field is mapped, but it: | :* The <tt>record_id</tt> field is mapped, but it: | ||
::* is empty | ::* is empty | ||
::* has a non-numeric value | ::* has a non-numeric value | ||
::* has a value outside the valid range of 1001 to 2<sup>31</sup> - 1 | ::* has a value outside the valid range of 1001 to 2<sup>31</sup> - 1 | ||
When a record is ignored (rejected), an entry is added to the [[Import Log]]. | |||
Latest revision as of 23:17, 4 May 2012
During an import, some incoming records may be ignored. (In general, you'll want to be sure that the number of ignored records reported in the Import Log matches the number you expect.)
Incoming records are ignored in the following circumstances:
- The object has a Unique Key Index, and the new record would cause a duplicate key.
- The record_id field is mapped, but it:
- is empty
- has a non-numeric value
- has a value outside the valid range of 1001 to 231 - 1
When a record is ignored (rejected), an entry is added to the Import Log.