How to Use Report Options and Print to PDF in SyteLine
how to save report options and print a report to PDF in SyteLine
Also searched as
- SyteLine report filter selection criteria
- SyteLine run report in background and email
- SyteLine report preview blank
- SyteLine default report parameters per user
Short answer
Most SyteLine reports are run from a form with selection criteria (the report options) such as ranges, dates and status, then sent to preview, printer, file or the background queue. Save your criteria so they are not retyped, and use a background run for slow reports. Blank output nearly always means the filters exclude every row.
Applies to: Infor SyteLine 8.x and CloudSuite Industrial 9.x and 10.x with SSRS-based reports. Behaviour of output options depends on the reporting setup.
How to run, save and export a report
- 1Open the report form from its menu (for example a customer, inventory or job report) and review the selection criteria fields.
- 2Enter ranges carefully: starting and ending values, date ranges, status checkboxes and the site. A blank To field is treated differently from a blank From field on some reports.
- 3Check the options such as sort order, detail or summary and whether to include inactive records.
- 4Choose the output: preview on screen, print to a printer, file or the background task if your release supports it.
- 5For PDF, preview the report and use the export or save option in the viewer, or select a PDF output type if offered.
- 6Save the parameter set under a name if the report form supports saved criteria, so you or your team can reuse it.
- 7For long reports, run in the background through the task queue and collect the result when finished, rather than keeping the form open.
- 8If the report is blank or slow, narrow the criteria and check the report's site and date filters first.
Why reports return no rows
Blank reports are a filter problem more often than a system fault. Typical causes are a date range in the wrong fiscal period, a status checkbox that excludes the records you want (for example only Open orders when everything is Filled), a site different from where the data was entered, or an item range where start is later than end.
Start by running the same report with the widest possible criteria. If rows appear, tighten one filter at a time. If nothing appears even with open criteria, then check permissions and data in the underlying table with a direct query.
Slow reports and background runs
A report that runs for minutes on screen should usually be run in the background so the client is not tied up and a timeout does not kill it. Scheduled and background runs also let you produce the same output every morning with the same criteria. The task manager page describes how background tasks are set up.
If one report is consistently slow, the cause is usually a wide date range on a large transaction table, a missing index on a custom filter, or a report that calls a heavy view. Narrow the criteria first, then look at the SQL Server execution plan if it remains slow.
Preview versus export and custom reports
Standard reports are delivered with the product and customized ones are usually built in SSRS or as custom stored procedures and views. When someone asks for an edit to a column or a header, check whether the report is standard, because upgrades can overwrite changes to standard report definitions.
For repeatable extracts, a SQL view or IDO is more stable than a screen report. The custom reporting page covers this. Use the delivered report for printed documents such as pick lists and invoices, and a view for data analysis.
-- Quick check that data exists for the report filters (verify names on your release) SELECT COUNT(*) AS rows_in_range FROM co WHERE order_date >= '2026-01-01' AND order_date < '2026-02-01' AND stat = 'O';
Common pitfalls
- !Assuming a blank report is broken instead of checking site, date, status and range filters.
- !Running a wide date range on a transaction report on screen and timing out the client.
- !Editing a standard report definition and losing the change at the next upgrade.
- !Relying on a screen report for large data extracts instead of a view or IDO.
- !Forgetting that a saved parameter set holds old dates and needs updating before reuse.
How an ERP-grounded AI assistant handles this
ERPray can answer many questions that people run a report for, such as open orders by customer or past-due jobs, directly over live data and show the query, without picking from a menu. It does not replace formal printed documents like invoices and packing slips. For compliance documents, keep using the delivered report forms.
Frequently asked questions
How do I export a SyteLine report to PDF?
Run the report to preview, then use the export or save control in the viewer and choose PDF. Some setups offer a PDF output type or a file destination on the report form. Use the background run if the report is large.
Why is my SyteLine report blank?
Most often the filters exclude every row: wrong site, date range, status or item range. Re-run with open criteria, then tighten one at a time. If still blank, verify the data exists with a direct SQL count.
Can I save report criteria for reuse?
Many report forms let you save and reload a named set of criteria, and background tasks store their own parameters. Check dates in saved sets before reuse, since they do not update on their own.
Why is a report very slow?
Usually a wide date range on a large table, a heavy view or a missing index behind a custom filter. Narrow criteria, run in the background and review the SQL plan if it persists.
Related
SyteLine error: an error has occurred during report processing
This generic SSRS error in SyteLine usually comes from one of three sources: the client cannot reach the configured report server URL, the report's data source credentials or connection string are wrong, or the report definition itself has a parameter or dataset problem. Check the report server URL setting in SyteLine first, then confirm the report is actually deployed to that server, then look at the SSRS server's own execution log for the real underlying error.
AdvancedHow to Build SQL Views for Custom SyteLine Reporting
Reports should read from purpose-built SQL views, not directly from SyteLine's core transactional tables, so an Infor patch cannot silently break them and heavy report queries do not lock rows the ERP itself needs. Put custom views in their own schema or under a clear naming convention, build them on stable base tables, and grant reporting tools read access to the views only.
AdvancedHow to Schedule a Background Task in SyteLine Task Manager
SyteLine's Task Manager lets an administrator schedule recurring background work - an MRP or APS regeneration, a report run, a custom IDO method, or an external program - without a user triggering it manually from the client. You define a task with what to run and on what recurrence, and the Task Manager background service picks it up and executes it at the scheduled time.
AdvancedHow to Improve SQL Server Performance for a Slow SyteLine ERP System
Most SyteLine performance complaints trace back to a handful of SQL Server issues: stale statistics, missing indexes on high-churn IDO tables, blocking caused by the default isolation level, and IDO Runtime connection pool exhaustion. Working through those systematically, with DMV evidence, resolves the majority of slow system tickets faster than guessing at application-layer causes.
Error fixFixing SyteLine's 'Object reference not set to an instance of an object' error
This is a generic .NET NullReferenceException surfacing through the SyteLine IDO Runtime, not a SyteLine-specific error code. It almost always means a form, script or IDO method referenced a field, row or object that came back null, usually after a customization, a missing related record, or a view/IDO method call before the form finished loading. Turn on detailed client logging and check the most recent customization or form event first.
Error fixDiagnosing and fixing SyteLine session timeout errors
SyteLine session timeouts come from one of three independent layers: the IDO Data Service session timeout on the app server, the IIS/application pool idle timeout for the web (Mongoose Web) client, or a load balancer/proxy idle timeout in front of a CloudSuite hosted environment. Fixing the wrong layer is the most common mistake - you need to identify which layer is actually expiring the session before changing anything.
AI for ERPAI for Infor SyteLine and CloudSuite Industrial
Add grounded AI to Infor SyteLine or CloudSuite Industrial: natural-language answers, agents over IDOs and ION, on-prem or CloudSuite deployment.
AI for ERPAn Air-Gapped Private LLM for SyteLine, Built for Defense Suppliers
Deploy a private LLM on an air-gapped network alongside Infor SyteLine for defense suppliers: no internet egress, ITAR and CMMC-aware architecture.
Stuck on Infor SyteLine (CloudSuite Industrial)?
Talk to engineers who work inside Infor SyteLine (CloudSuite Industrial) every week, and who build private AI that answers these questions from your own ERP data.