search

Cadasta / cadasta-docs

Documentation for Cadasta legacy platform
GNU Affero General Public License v3.0
3 stars 2 forks source link

Import Chapter :: Issues users may run into and suggested solutions #14

Closed SteadyCadence closed 7 years ago

SteadyCadence commented 7 years ago

The import process can be tricky if there are required fields missing or the values do not match up perfectly.

I suggest we dive into some errors that may occur so that the user is aware of what may happen if the import is not properly formatted/matched up, etc.

Maybe something like "Common Issue :: Solution" near the bottom of the chapter (it can be an add on or extension).

Some Common Problems:

  1. Too large of an import (imports can only handle so many records at this time)
  2. Poorly spelled or not matching field names or values
  3. Values that do not map to the choice values listed in the form
  4. Mismatched columns (an error in the 2nd step with matching up the column headers to the form names)
  5. Improperly formatted geo column
  6. Missing required fields (location_type, party_name, tenure_type, party_type, etc)
SteadyCadence commented 7 years ago

Select_multiple values must be importing like "optionA,optionB"

SteadyCadence commented 7 years ago

Upload some good import files.

bethschechter commented 7 years ago

Note: if it's in a CSV, then select_multiple needs to be a list with quotes around it

bethschechter commented 7 years ago

@SteadyCadence I've added this. Closing the issue, but of course reopen or whatever if it needs to be edited when you review.