OneView Properties
OneView Properties
Sign in Create account
For property managers

Fix import errors

Read the list of problems an import shows, correct the rows in your spreadsheet, and upload again.

Before you start

An import is all or nothing. If even one row has a problem, OneView imports none of it and shows the list of problems at the top of the import page, in a red box. Nothing was saved, so you can't damage anything by trying again.

Keep your spreadsheet open. You will fix it there and upload it again. This article follows the import described in Import properties, units and tenants from a spreadsheet.

1. Read the list of problems

The red box has one line per problem, with these columns:

  • File: which file, the properties file or the tenants file.
  • Row: the row number as your spreadsheet shows it, header row included.
  • Column: the column to look at.
  • Value seen: what OneView read in that cell.
  • Problem: what is wrong.

If your file has a lot of problems, the list shows the first ones. Fix those and upload again, and the next ones appear.

2. Fix the rows in your spreadsheet

Go to the row and column named in the list and correct the cell. The most common problems are:

  • A required value is missing. The message reads "is required". Fill in the cell.
  • A date is not understood. "is not a date. Use day/month/year, e.g. 25/09/2025 (or 2025-09-25)". Type it as day/month/year. paid_through is a month instead: "is not a month. Use month/year, e.g. 10/2026 (or 2026-10)".
  • paid_through is off the rent cycle. On a lease paid every few months, paid_through must be the last month of a period, counted from rent_starts. The message names the two nearest months that fit.
  • An amount has decimals or a currency sign. "is not a whole-franc amount (e.g. 50000 or 50 000)". Use whole francs only.
  • A phone number is wrong. "is not a valid phone number (e.g. 670000001, or +2250700000000 with the country code for a number outside Cameroon)".
  • An email is wrong. "is not a valid email address".
  • A tenant has no contact. "each tenant needs a WhatsApp number or an email". Add a WhatsApp number or an email on that row.
  • An amount due has no reason, or a reason has no amount. "amount_due needs a due_reason (what the money is for)" or "due_reason needs an amount_due (how much is owed)". Fill in both cells, or empty both.
  • The part already paid covers a whole period. "is a whole rent period or more (…). Move paid_through forward a period instead". rent_partly_paid is only for a period the tenant paid part of.
  • The same unit appears twice. The message names the first row where it appears. Each property and unit pair can appear once in the properties file, and once in the tenants file because one unit has one lease.
  • A tenants row names a unit that doesn't exist. The message quotes the property and unit it looked for. Correct the spelling so it matches the properties file exactly, or add the unit to the properties file.
  • A building is in two groups. A property belongs to one group. Use the same group on all of its rows.
  • paid_through is before the lease start. "is before rent_starts. If nothing is paid yet, use the month before rent_starts".

Two other messages are about the whole file. "no data rows found below the header. Rows starting with EXAMPLE are skipped." means there is no row to import under the header: the file is empty below it, or every row starts with EXAMPLE, which older templates used for their examples. A message about missing columns means the header row doesn't match the template, so compare it with the template you downloaded. A tenants file made from an older template, with a next_rent_due column, is refused this way: download the template again and fill in paid_through.

3. Upload again

The import page is still open under the red box. Choose the corrected file again with Choose file and select Check my files. Upload both files again if your tenants file uses units from a properties file that was never imported. If the list is gone, open Import data again.

What happens next

When the files pass, you reach the summary page, where you can check what will be created and select Import now. Warnings on that page, in the Worth a look box, don't block the import. Typical ones: a row that looks like a sample line will be ignored, or a unit that already has a lease will be skipped.

Common problems

I fixed the file but the same errors come back

Check that you saved the file before uploading, and that you picked the corrected file. Save as .xlsx or .csv.

OneView says it can't read my file

The message asks you to save the file as .csv or .xlsx and try again. Open it in your spreadsheet app and use Save as with one of those formats.

Some rows failed after the import ran

This is different from the list above: the file was valid but a few rows could not be saved. The status page lists them under a heading such as "1 row could not be imported:" with their file and row number, and everything else was imported. A tenant whose email or phone number already has a OneView account can't be imported: invite that person from Tenants in the menu instead. For other rows, correct the file and upload it again. Rows already imported are skipped, so nothing is duplicated.

Some rows were skipped

The status page shows them as skipped because they already exist, for example a unit that already has a lease. Nothing is wrong, and nothing was duplicated.