Work order traveler prints incomplete routing steps — fix missing operations

Joe B.

Expert ★★★★★ 27,853 satisfied customers

Specialities: ERP/MES reports, SSRS & Crystal, Zebra/Laser printers, BOM/Routing, shop travelers

Traveler/routing report missing steps — SSRS/Crystal filters, LEFT JOINs, page breaks, group options, scaling, printer margins

Technician

Hi! We’ll get your work order traveler to print the full routing steps/operation sequence with setup/run times, work centers, and instructions intact.
A few questions to pinpoint the cause: Which ERP/MES and report tool are you using (SSRS, Crystal Reports, BarTender PDF)? Are the missing operations specific to subcontract or rework steps, or does the traveler truncate at a page break? And are you printing to PDF, a laser printer, or Zebra thermal?

Customer

We’re on Microsoft Dynamics 365 with SSRS. Some travelers show steps 10–40 but skip 50–60 (outside processing). Others stop at step 30 when the page breaks. Export to PDF looks fine but the printed copy is missing operations. Receiving complains the routing steps are incomplete.

Technician

Understood. Typical reasons a traveler prints incomplete routing:
• Dataset uses an INNER JOIN from routing to operations, so steps without time/notes or subcontract flags drop out — use LEFT JOIN to keep “empty” rows.
• Report parameters filter by Released status only; Pending/Planned ops or Outside Process get excluded.
• Group/page settings: “Keep together” combined with a small margin can push a group off the page and hide steps after the break.
• Printer scaling: browser/driver shrinks/expands → the last line is clipped. 100% scale, no “Fit to page,” correct Letter/A4 and margins.
Plan: 1) Fix query & joins. 2) Loosen filters. 3) Adjust SSRS group breaks and CanGrow. 4) Lock print scaling and margins.

Customer

Can you outline the exact report settings we should change? We also have Crystal for legacy travelers.

Technician

Step 1 — Query & mapping
• Ensure Routing → Operation is a LEFT JOIN; include WHERE wo = @WorkOrder but avoid conditions on operation fields that null out subcontract steps.
• Sort by Operation number (pad to 3–4 digits: 0010, 0020…).
• Include fields used by parsers: Work center, Setup/Run, Queue/Move, Instruction text, Outside processing vendor.

Step 2 — Filters/parameters
• Traveler type = Released + Planned. If you must filter, add checkbox “Include outside processing / subcontract”.
• For partial travelers, ensure “From step/To step” range covers all ops; zero-pad compares as strings if not numeric.

Step 3 — SSRS/Crystal layout
• Set tablix/group: Repeat header on each page, Keep together = False for the detail group, and Page break at end of WO group only.
• Allow textboxes to CanGrow and set row height minimums so long instructions don’t hide the next row.
• Margins: 0.25–0.5″. Increase body width to avoid truncation; ensure the width + margins ≤ page width.

Step 4 — Print pipeline
• Export to PDF then print at 100% scale. Avoid browser viewers that insert headers/footers or shape the page to A4 when you use Letter.
• Laser printers: disable “Fit to printable area”. Zebra: use a ZPL-format traveler template sized to the label; don’t auto-scale from an A4 PDF.

Customer

Some of our routings have alternate operations and ECO revisions. Could that hide steps too?

Technician

Yes. Include effective dating/ECO in the dataset so the traveler selects the correct revision at the work order start date.
• Add predicates: EffStart ≤ @WODate and (EffEnd is null or EffEnd ≥ @WODate).
• For alternate work centers, coalesce to the chosen path for the WO (routing selection table). Otherwise you’ll see gaps where the primary op is suppressed.
• If the system stores phantom/subassembly ops, ensure the view includes them even when backflushed.

Customer

We noticed operations disappear when long instructions wrap. The next row seems to vanish at the bottom of the page.

Technician

That’s pagination. Two fixes:
• In SSRS, turn Keep together off on the detail row and Allow height to increase (CanGrow). Don’t fix row height; let the table split across pages.
• Increase bottom margin slightly or reduce font leading by 0.5–1 pt so the last row doesn’t collide with the footer. Print from the PDF viewer at Actual size, not “Fit”.

Customer

We also generate a shortened traveler for picking. Could that custom filter be leaking into the main report?

Technician

It can. Make sure the intake/pick traveler uses a separate dataset or parameter set. Clear shared report cache/snapshots so old parameters (like “Only machine ops”) aren’t reused. Name parameters explicitly: @IncludeSubcontract, @IncludeSetup, @FromOp, @ToOp.

Customer

After the changes, PDF shows all steps, but our laser printers still cut the last line of page 1.

Technician

Final print tune-up:
• Set PDF print to 100% / Actual size; disable “Fit to printable area”.
• Choose the correct paper size (Letter 8.5×11 vs A4) and margins 0.25–0.5″.
• In driver properties, turn off “Shrink to fit”, “Scale to 96%”, or “Borderless”.
• If your ERP prints via browser, export to PDF first; some viewers add headers/footers that clip the table.

Customer

That worked. Any governance tips so new routings or ECOs don’t break the traveler again?

Technician

Governance checklist:
• Store operation numbers as numeric (10,20,30) and display with padding (0010) — prevents sort bugs.
• Validate alt routings and outside processing on a test WO before release.
• Lock report versions in source control; publish with a semantic version to avoid parameter drift.
• Keep a “golden” multi-page traveler PDF to test page breaks after every ERP update.

Customer

Perfect — the traveler now prints all routing steps and instructions on every page. Thanks!

Technician

Summary: If a work order traveler prints incomplete routing steps, change the dataset to LEFT JOIN, widen filters to include outside processing and planned ops, fix SSRS/Crystal group breaks and CanGrow, then print at 100% scale with correct margins. Need help editing the query or RDL/RPT? Open the chat.

Quick answer: the accepted fix

Accepted fix when a work order traveler prints incomplete routing steps: convert INNER to LEFT JOIN so empty/subcontract ops remain; include Released + Planned ops; set SSRS/Crystal groups to allow page breaks and CanGrow; export to PDF and print at Actual size with correct Letter/A4 margins.

FAQ

Step-by-step (Windows 11)

1. Edit the report query to LEFT JOIN routing→operations; include Released and Planned operations.
2. Set SSRS/Crystal group options: Repeat header; Keep together = False; enable CanGrow for instruction text.
3. Export to PDF and print at Actual size with correct paper size and margins.
4. Test with a long WO including outside processing and long notes to confirm page breaks.

Note for mixed environments (macOS)

1. When printing PDFs from macOS, disable “Scale to fit” and keep 100% zoom.
2. Use vendor drivers in CUPS for laser printers; keep Letter/A4 consistent with Windows settings.

Sources

• Microsoft — SSRS pages, margins, and paper sizes
• SAP Crystal Reports — grouping and pagination
• SSRS — grouping, sorting, and KeepTogether

Matt ● replies in < 1 min

Technician Expert

⭐⭐⭐⭐⭐ Trusted by 27,000+ customers

Alex · Expert's Assistant

Start Chat

5 Tech Support Specialists are online right now.