If an import saved the wrong information, open the affected records and find exactly what needs changing. Correct those records through their normal actions or a new Update import. The original import stays in history so someone can understand what happened.

Before you begin

You need the import type’s viewing permission to open its history or files. Correcting records requires the matching management permission, such as Manage positions, Manage employees, Manage labor budgets, or Manage actual compensation. Running a replacement import also requires the applicable import permission and coverage for every affected department and date in the complete file. Downloading a source or result file also requires the matching export permissions.

Review what changed

Open the import summary, review its issue summary and row sample, and open the original submitted file if needed. Identify the affected record, field, earlier value, new value, and effective date.

Do not begin by uploading the same file again. First determine:

  • whether the import completed;
  • which rows were created, updated, unchanged, or skipped;
  • whether the value, date, individual record, or set of records was wrong;
  • whether later authorized work already changed an affected record; and
  • whether the correction belongs on the record page or in a new import.

Keep the original file and completed summary with the people allowed to review them. They show what was imported before the correction.

If the import affected many records or private information

When a completed import exposes protected information incorrectly, changes a large set of records, or affects active business work:

  1. stop preparation of any related duplicate import;
  2. tell the responsible organization owner what completed;
  3. limit further use of any incorrect exported or downloaded files;
  4. identify all affected departments and records;
  5. review active requests, assignments, financial results, or reports affected by the change; and
  6. contact Support before another broad update when the safe correction is unclear.

Do not delete or rewrite activity in an attempt to hide the mistake.

Choose the correction

Use a new update import for a consistent bulk correction. Use the record page when only a few records need attention and the available correction action matches what happened. Keep position control, labor budget, and actual compensation corrections in their own areas.

What happened Correction approach
A value or effective date was recorded incorrectly Correct the existing record using the action provided for that information
A valid value should change later Add a later dated business change rather than rewriting the earlier period
A record should never have been created Use the remove or void action when the page confirms it matches the situation
Many rows need the same safe correction Prepare a new Update file with only the affected rows
The affected set or correct dates are uncertain Stop and contact Support before another broad file

Example: wrong future department date

An import moved separate Evergreen Health practice positions to Inpatient Services beginning June 1, but the approved date is July 1.

If the June 1 date was never valid, prepare a correction that restores the accurate timeline, using the position correction action supported by the template or record page. Do not add another Inpatient Services change on July 1 while leaving the false June period in history.

Review active requests and department-based access that may have been affected during the incorrect period.

Validate the correction as carefully as the original file, then review the affected records and activity.

For employee compensation, use correct when an entry was wrong, default to record use of employee-level pay or no employee-level pay from a date, and remove when the entry should never have existed.

Example: stop using a pay override

An assignment-specific pay value should give way to employee-level pay on October 1. Use default with October 1 as its effective date. This adds a dated default selection and retains the earlier pay entry. To stop employee-level pay instead, record a default selection for the employee. Pay entries have no end date.

Preview the correction and check the saved result

  1. Include only the records that need correction.
  2. Download a fresh Update template.
  3. Confirm stable identifiers and dates.
  4. Validate the file and compare each preview change with the intended correction.
  5. Review warnings and active requests again.
  6. Apply once.
  7. Review a date before and after the corrected period.
  8. Run new reports after related results finish updating.
  9. Review Activity history to confirm the original import and correction form an understandable sequence.

A completed report prepared before the correction will not change. Preserve it when it is needed for review and run a new report for the corrected result.

If you do not know which records need fixing

Contact Support before applying another large file when you cannot determine every affected record or the correct dated action.

Include the import number, type, mode, completion time, affected departments, approximate row count, example records, and the intended business result. Do not include passwords or unnecessary protected values.

Optional practice: fix one wrong imported value

Use prepared practice records for this exercise. Follow its setup instructions before making changes.

  1. Open the completed import and the affected record.
  2. Compare the file, the saved value, its date, and any newer changes.
  3. Decide what is wrong: the value, date, record, or set of records.
  4. Use the record’s correction action, or prepare a fresh Update file containing only the records that need fixing.
  5. Validate, apply once, and check dates before and after the correction.

If a valid rate or pay amount changes later, add a new effective-dated value or use the supported default action. Rates and pay values have no end date. If the entry was never correct, use the appropriate correction or removal action.

For a partly completed import, first find which rows already succeeded. Do not repeat successful Create rows. Run a new report after the corrected results finish updating.