Issues to Resolve — One RO, All, Unattached
Issues to Resolve — the issue list — Operator Guide
This is the working list where you actually clear import issues. You get here three ways, and all three look and behave the same:
- From the summary. The tile RO Import Issues to Resolve opens the summary (one row per order — see the separate Issues to Resolve — Summary guide). Clicking a row opens that order's issues; the heading then reads Issues to Resolve — RO 700123.
- See all issues on the summary — every issue across every order, one flat list.
- Unattached row on the summary — issues that belong to no order at all, because the import gave up before it could create one. Heading reads — Unattached.
Every version has ← Issues Summary at the top left to get back.
Step by step
- Pick the list you want (one RO, all, or Unattached).
- Use the chips to narrow it: the first row of chips is the status — Open, Resolved, Ignored, All (it opens on Open). The second row is the issue type. Chips combine with the search box; you keep your other filters when you click one.
- Search by title, SKU, source reference or the detail text, then Apply.
- Work the rows. Oldest first — the Age column turns red at 7 days and over.
- Click Resolve or Ignore on the row. Some types ask you a question first (below). You can also add a short note; it is optional and it is kept.
- On Open, a row you close disappears from the list and the count drops. On any other status filter the page reloads instead.
To do several at once, tick the boxes on the left, then use Resolve selected or Ignore selected in the bar that appears. Bulk asks for one note that applies to all of them — bulk cannot supply a SKU or a quantity, so bulk-resolving a "SKU not in QB" or "no qty" issue will report an error for that row and leave it alone. Do those one at a time.
What the columns show
| Column | Meaning |
|---|---|
| Age | Days since the issue was raised. Red and bold at 7+ days. |
| Type | Which kind of problem it is (see below). |
| Title | The short description the import wrote. |
| SKU / Ref | The SKU, or the source reference if there is no SKU. |
| Qty | The quantity on the line, if the import found one. |
| Source Ref | The BOM / file reference the line came from. |
| Order | The RO number — click it to open the order. Blank on Unattached issues. |
| Detail | The long explanation. Click it to expand it. |
| Actions | Resolve / Ignore. Hidden entirely for view-only users. |
The issue types
| Type | What it means |
|---|---|
| SKU not in QB | The BOM named an item we don't have. Resolve asks you for a real SKU and converts the line to an inventory line under that SKU. Ignore leaves it as a non-inventory line — that is a legitimate answer for one-off buy-outs. |
| no qty | The line arrived with no quantity. Resolve asks for the quantity and writes it on the line. There is no Ignore button — a line with no quantity can't be picked or ordered. |
| unmatched job | The import could not tie the BOM to a job. |
| duplicate line | The same item appears twice on the import. |
| header only | The file had a header but no usable lines. |
| unmatched NONINV refresh | A re-import could not line up a non-inventory line with the one already on the order. |
| unlinked QB PO | A purchase order we can see does not tie back to an RO line. |
Everything except the first two resolves as a note-only stamp: you are recording that you looked at it and it's handled.
What happens after
- The issue is stamped Resolved or Ignored with your name and the time.
- A line that was on HOLD because of it comes off hold automatically once its last open issue is closed. You never clear a hold by hand. (Lines somebody set to Cancelled or Closed Short stay that way — that's a human decision, not an issue.)
- Everything is written to the order's history, including the note you typed.
Common mistakes
- Ignoring a "SKU not in QB" that should have been resolved. Ignore means "this stays a non-inventory line forever". If it is a stock item, add the item first on Create New Inventory Item, then Resolve with the new SKU.
- Typing a SKU that isn't in the item master. You get SKU … is not in IM2 — add the item first. Nothing is changed.
- Bulk-resolving typed issues — see above; use the row buttons.
- Wondering where the rest of the issues went. You are probably on a per-RO list. The N open badge beside the heading is the count for the whole system, not for the list in front of you.
- Nothing showing. The status chip defaults to Open; click All to see history.
Non-inventory lines: Use Surplus (added 2026-09-07)
A non-inventory line now has three answers, not two:
| Button | What it means | What happens |
|---|---|---|
| Resolve | It really is a stock item | Enter the SKU; the line becomes an inventory line and is picked from stock |
| Use Surplus | We already own one — used/surplus equipment on the shelf | The line is marked SURPLUS: it drops off the buy list and is not drawn from QuickBooks inventory |
| Leave Non-Inv | It is a genuine outside buy | The line stays non-inventory and goes to Purchasing to be bought |
UOM is now shown next to the quantity, read off the RO line the issue points at.
Issues with no RO number behind them appear under the Unattached view. They are not failed imports — an import that fails creates no RO and no issue at all — they are notes raised against a source document (for example a FieldPulse material list that was empty), and they are closed the same way.
A SKU line must have a quantity (added 2026-09-07)
If a line carries a SKU but no usable quantity, Resolve asks you for the quantity and will not save without one greater than zero. Ignore is not offered on those lines — a SKU with no quantity can't be picked, ordered or issued, so the number has to be supplied. This holds however the issue is labelled (no qty, Qty problem, or a review flag): the screen looks at the line, not the label.
Non-inventory lines are unaffected — they still offer Resolve, Use Surplus and Leave Non-Inv.
Sorting the list (2026-09-07)
Click any column heading to sort the list by that column; click it again to reverse. Blank cells always fall to the bottom. Numbers sort as numbers and dates as dates. Button and checkbox columns (Actions, Detail) don't sort. The sort works on the rows already on screen, so it never hides anything the page was showing.