Troubleshooting
When CensusIO stops you, it tries to say exactly why in plain language. This section collects those messages, grouped by where they happen, and tells you what each one means and how to clear it.
Where messages appear
Section titled “Where messages appear”- In a form, when you save a record: the fields that need fixing are highlighted with a short note under each one.
- In the import preview, before anything is saved: a count of valid and invalid rows, with the failing rows listed and the reason on each field.
- On a sync or collector, after the fact: failures are kept and shown on the survey type’s failures page, so a bad submission never blocks the good ones.
- At the top of a page, as a short banner, when an action cannot proceed (for example, a plan limit).
A message is not a dead end. Almost every one names the thing to change, and your data is not lost while you fix it: a failed import row, a rejected record, or a failed sync submission all stay where they are until you correct them.
In this section
Section titled “In this section” Sign-in and plans Signing in, joining an organization, and plan limits.
Imports and syncs File imports and the Kobo, ODK, and ArcGIS connections.
Records and review Field validation, the review workflow, and publishing.
Maps, files, and feeds Map layers, attachments, locations, the BI feed, and collectors.
Collecting with the apps The mobile and desktop apps: connecting, offline sync, photos, and conflicts.