I know this is an odd request since standard operating procedure is to convert/promote a Target into a Lead, however I think we picked up some bad advice when we first deployed our system back in 2018 and we would like to migrate substantially all of our 1,400 “Leads” into “Targets” in order to clean things up.
I’m super adept at SQL and if the worst case is to do a SELECT INTO I’m down to clown.
Getting the following errors dumped out with any import:
NOTICE: [8] Uninitialized string offset: 0 on line 156 in file /www/SuiteCRM-7.10.10/vendor/zf1/zend-search-lucene/library/Zend/Search/Lucene/Storage/File.php
NOTICE: [8] Uninitialized string offset: 1 on line 157 in file /www/SuiteCRM-7.10.10/vendor/zf1/zend-search-lucene/library/Zend/Search/Lucene/Storage/File.php
NOTICE: [8] Uninitialized string offset: 2 on line 158 in file /www/SuiteCRM-7.10.10/vendor/zf1/zend-search-lucene/library/Zend/Search/Lucene/Storage/File.php
I found the Search settings and added the module to the enabled list, but will need to figure out how to trigger some re-indexing or try re-importing again
Some people use a workflow for “all records” to change some field in each record, causing it to run the indexer. (make sure your workflow runs only once, and off business hours)
Yes the scheduler jobs were running – at least the last run dtstamp was getting updated – just no activity visible in the /Index/Index directory and in fact it looks like it has not done anything in years:
root@crm:/www/suitecrm/modules/AOD_Index/Index/Index# ls -alt
total 2388
-rw-rw-rw- 1 www-data www-data 0 Mar 16 16:04 read.lock.file
drwxr-xr-x 2 www-data www-data 126976 Jan 15 2021 .
-rw-rw-rw- 1 www-data www-data 0 Jan 15 2021 _5xcem_t.del
-rw-rw-rw- 1 www-data www-data 0 Jan 15 2021 _5xcem_u.del
-rw-rw-rw- 1 www-data www-data 0 Jan 15 2021 _5xcfe.sti
-rw-rw-rw- 1 www-data www-data 0 Jan 15 2021 _5xcff.cfs
-rw-rw-rw- 1 www-data www-data 0 Jan 15 2021 _5xcfg.fdt
-rw-rw-rw- 1 www-data www-data 0 Jan 15 2021 _5xcfg.fdx
-rw-rw-rw- 1 www-data www-data 0 Jan 15 2021 optimization.lock.file
-rw-rw-rw- 1 www-data www-data 0 Jan 15 2021 read-lock-processing.lock.file
-rw-rw-rw- 1 www-data www-data 0 Jan 15 2021 segments_buna0
-rw-rw-rw- 1 www-data www-data 0 Jan 15 2021 segments_buna1
-rw-rw-rw- 1 www-data www-data 0 Jan 15 2021 segments_buna2
-rw-rw-rw- 1 www-data www-data 20 Jan 15 2021 segments.gen
-rw-rw-rw- 1 www-data www-data 0 Jan 15 2021 write.lock.file
-rw-rw-rw- 1 www-data www-data 0 Jan 15 2021 _5xcem_p.del
-rw-rw-rw- 1 www-data www-data 0 Jan 15 2021 _5xcem_q.del
-rw-rw-rw- 1 www-data www-data 0 Jan 15 2021 _5xcem_r.del
-rw-rw-rw- 1 www-data www-data 0 Jan 15 2021 _5xcem_s.del
-rw-rw-rw- 1 www-data www-data 0 Jan 15 2021 _5xcf9.sti
-rw-rw-rw- 1 www-data www-data 0 Jan 15 2021 _5xcfa.cfs
I tried deleting the lock files first, and then tripping off the reindex and then the whole directory over per your instructions and- it never recreated the directory, so i created it and tried again and never saw any evidence that it was creating files in it so i just moved it back and restored the database
I literally JUST installed Elastic yesterday when it was evident that the internal indexing system was not functioning correctly (eg, not indexing the Targets / Prospects table)
Sorry, my bad, I confused Lucene with Elastic, they’re different things. I think Lucene works, if you can get around the problems.
But if you were able to get Elastic up and running, which is something not everybody less-technical can achieve, you now have a much more modern and better system, so…