CiviCRM Community Forums (archive)

Idea of this module is to provide a base UI for importing - a stripped down version of the current interfaces available for contacts, contributions, memberships, etc., which allows users to import files into CiviCRM and do complex processing as part of the import.

Hopefully, it will be able to leverage / compliment the api-ification of importing discussed here http://civicrm.org/blogs/lobo/implementing-batch-import-api.

The idea comes from the following use case:

    * We are integrating with a legacy finance system that delivers a record of payments.  We have no chance of people able to get an api for this system or anything similar.  We'll likely move away from this system at some point in the future but need this integration in the mean time.
    * What we are importing is two things: contacts, and contributions.  but there are a few things that we need to do as these objects are going through the system, e.g. depending on the values in the contact csv, we want to create a pending membership; depending on the values in the contributions csv, they should actually be treated as membership imports and the membership end date be moved on by a fixed amount.
    * We want to carry out some actions based on the values of some of the fields in the import, but we don't need to store these fields
    * We don't need to map fields for this custom mapping.

One approach would be to use hook_civicrm_post to fire off these rules (and I could definitley be convinced of that if it seems easier) but this approach would do the following

Allow a user to specify a csv file to upload (like step step 1. Upload Data)

Step 2 - I don't think is necessary because essentially this is fixed in a custom import.

Do some testing (like step 3. Preview)

Report on the import (like step 4. Summary)

We could probably do this using a saved field mapping and some hooks that get fired when these imports are created.