... | ... | @@ -31,4 +31,15 @@ |
|
|
_KJC 2022-01-25_
|
|
|
|
|
|
|
|
|
In addition to `civicrm_json_importer_failure` getting crazy large due to notices, warnings and errors, I have found that failed import leave the table `civicrm_queue_item` full of queued items. For example today jsimport test site has 900,000 rows of unneeded data. |
|
|
\ No newline at end of file |
|
|
In addition to `civicrm_json_importer_failure` getting crazy large due to notices, warnings and errors, I have found that failed import leave the table `civicrm_queue_item` full of queued items. For example today jsimport test site has 900,000 rows of unneeded data.
|
|
|
|
|
|
|
|
|
_KJC 2022_02_02_05_
|
|
|
|
|
|
#### Ran a 30,000+ record import and the following quirks were discovered
|
|
|
|
|
|
- We deleted an address row `supplemental_address_3` and it did not get properly removed. It left a constant `primary_address_3` in the DB
|
|
|
- We mapped column `external_id` to the CiviCRM field `external_id` and it added `external_id` as a constant.
|
|
|
- remapped to a custom field and it still mapped as constant
|
|
|
- Changed columns name in a new import to `ext-id` -- imported perfectly
|
|
|
- Need to review code as it seems naming a columns the DB column name is causing issues. |
|
|
\ No newline at end of file |