Skip to Help content

Reports & data

Validate CSV data and request an import commit

Use the correct CSV template, resolve row issues, and request processing of the exact reviewed data.

300 characters remaining

Quick links

Objective

Create a validated import batch and request its commit without confusing the request with a completed import.

Before you begin

  • Use the Studio owner's authorized account and approved source data. Keep a copy of the original CSV.
  • Have existing family, location, category, or billing account references ready for the chosen import. Opening balances need an approved financial review.

Instructions

  1. Open Settings > Imports and choose Import type

    Choose Families & contacts, Dancers & family matching, Classes & sessions, or Opening balances. Use the matching Download blank CSV template link at the bottom of the page.

  2. Fill the template without renaming its columns

    Keep the template headers and add at least one data row. Supply references from this studio. For Opening balances, amount_cents uses whole cents and currency uses three uppercase letters; have the amounts checked before continuing.

  3. Choose CSV source and inspect Column mapping

    Select a CSV smaller than 15 MB. Check the selected filename and each source column. If any column says Unsupported, correct the file before staging; this page shows the mapping rather than offering manual remapping.

  4. Select Stage and validate

    Read the batch summary and Validation issues for that batch. Use Batch, Row, Column, and Issue to correct the CSV. Select the corrected file and run Stage and validate again, then identify the newly validated batch.

  5. Request commit for the reviewed batch

    When its status is dry run ready and the exact source is available in the current session, select Request commit. Orbit checks the same data again. Read the resulting status rather than assuming the records have already been created.

  6. Verify the request outcome

    Check the batch name, version, summary, and committing status. Retain the approved file and batch details for follow-up. Verify the eventual records in their owning workspace before reporting an import as complete.

    Result: The validated batch has a saved commit request. A committing status confirms the request, not completed family, class, dancer, or balance changes.

Troubleshooting

The CSV has invalid columns, duplicate headers, or an unclosed quoted value.

Return to the matching blank template. Keep unique headers, use the same number of columns in every row, and close quoted values. Save the corrected CSV and select it again.

Validation reports unresolved references or invalid amounts.

Confirm family, location, category, or billing account references belong to this studio. Use integer cents for opening balances and a positive whole-number class capacity. Have the Studio administrator resolve disputed source values before restaging.

Request commit is disabled after I return to the page.

Reselect and revalidate the exact approved source in the current session. Use the newly validated batch; do not assume a previous browser session still holds the reviewed file.

The commit result is unknown or remains committing.

Refresh and check the batch before making another request. If the connection failed while the current session remains open, retry the same request when it returns. Contact Orbit support if the saved state remains unclear; do not start another import to force completion.

Result

Monitor the saved batch and verify resulting records before relying on imported data. This page does not provide an undo or a completed-import guarantee.

Support

Ask a Studio administrator to approve source corrections and any opening balances. Contact Orbit support for a stuck commit request, changed validation that cannot be resolved, or unclear resulting records.