Changes between Version 3 and Version 4 of Onyx to CiviCRM
- Timestamp:
- 12/09/13 13:58:33 (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Onyx to CiviCRM
v3 v4 49 49 - Since interviews can be updated if they have not been completed, the procedure will have to cope with updates as well as inserts. 50 50 - Since the cron jobs are run in a user's request, make sure that only a few participants are processed for each request. 51 - It is possible to have hidden custom fields within CiviCRM by [http://book.civicrm.org/user/current/organising-your-data/custom-fields/ marking the Custom Group as inactive]. This could be used to store a date last updated or a hash value to cut down the number of interviews that need to be processed every time. 51 52