Interface Core C · Industry convention Platform: Web

Data Import Workflow

A data import workflow checks an uploaded file, matches its columns, previews changes, and reports every import result.

See how it works
You might call it import wizardCSV import flowbulk data import

See how it works

Original worked exampleData Import Workflow

Another example

An admin maps a CSV email column, finds two bad rows, and imports the other 98 rows as one background job.

Main parts

  1. 01Source file
  2. 02Field mapping
  3. 03Validation rules
  4. 04Change preview
  5. 05Background job
  6. 06Row-by-row result

Use it when

Use it when people need to move many records from a file into an app safely and visibly.

Do not use it when

Do not import before showing the mapping and result counts. A retry must not create the same successful rows twice.

Name used in code

upload → map → validate → preview → background import → row results

Before you ship

Before release, check the page structure, keyboard access, visible focus, contrast, and zoom. Also check loading, empty, error, success, cancel, and reduced-motion states.

Request you can copy

Outcome: Use Data Import Workflow to solve this user need without losing the current context. User context: An admin maps a CSV email column, finds two bad rows, and imports the other 98 rows as one background job. Recommended pattern: Data Import Workflow. Why it fits: Use it when people need to move many records from a file into an app safely and visibly. Do not use it when: Do not import before showing the mapping and result counts. A retry must not create the same successful rows twice. Product requirements: Define the default, loading, empty, error, success, and recovery states. Keep user input. Give clear feedback after every action. Accessibility and resilience: Use semantic HTML, full keyboard access, and visible focus. Make the layout work when zoomed and support reduced motion. Follow the project’s current rules. Do not add a new UI library unless the project already uses it. Acceptance criteria: The main task works with keyboard only and at 320px width. Focus and status changes are announced. Check loading, failure, retry, cancel, and reduced-motion paths. Evidence and limits (evidence boundary): No single official standard controls the whole term. Its meaning may change across teams, platforms, or frameworks. Unknowns to confirm: Product wording, data source, analytics events, supported devices and languages, and platform limits.

Check this request

Review the current use of Data Import Workflow. Definition: A data import workflow checks an uploaded file, matches its columns, previews changes, and reports every import result. Release checks: Before release, check the page structure, keyboard access, visible focus, contrast, and zoom. Also check loading, empty, error, success, cancel, and reduced-motion states. Before changing code, report the evidence you found, gaps, severity, and the smallest safe fix.

C
How official is this term?

Industry convention

People often use this term at work. The listed sources may support practice or limitations. They do not define every part of the term.

No single official standard controls the whole term. Its meaning may change across teams, platforms, or frameworks.

Scope
Cross-platform data-import convention; Microsoft documents one Dataverse job model
Document status
stable
Checked on
2026-07-30

Evidence sources & scope

Authority source + Term reference · Microsoft Dataverse · stable Import data Scope: Microsoft Dataverse source files, field maps, validation, asynchronous import jobs, and error logs Role here: Direct term reference Source covers: canonical name, definition, semantics, implementation, usage guidance

Copy it yourself

The browser could not copy this. Select the request below and copy it yourself.