Bulk Import Review and Commit Guide

Row states

Bulk import creates or updates many records quickly, so review makes the result trustworthy. Ready rows can commit. Warnings can often commit but deserve a look. Errors need correction. Duplicates need a create, update, or skip decision. Ignored rows are intentionally left out. Keep important historical context as source evidence rather than forcing it into an asset.

Bulk actions

Use selected-row actions when you've inspected a chosen group needing the same fix, such as setting facility for 25 assets from one site or category for selected AHU rows. Use all-matching actions when the same issue spans the batch and the correction is safe everywhere, such as replacing a blank facility with the default or normalizing a category spelling. Be more cautious with all-matching actions, since one broad action changes many rows.

Duplicates, preview, and pattern

For duplicates: choose Update when tag or serial matches and the facility makes sense, Create when location or tag proves they differ, Skip or Ignore for repeats and note-only lines, and leave unresolved if unsure. Read the commit preview like a change request, checking create and update counts, skips, recognized vendor, PM, and parts context, source evidence, plan-limit exclusions, and dedupe collapses. For large files, review in passes: fix mapping, fill facility and location gaps, resolve duplicates, ignore irrelevant rows, preview, then commit.