SyteLine Report Viewer: Preview, Export and Schedule Reports (SSRS and Background Tasks)
syteline report viewer
Also searched as
- infor csd report scheduler
- sightline reporting
- infor syteline soc report
Short answer
In SyteLine / CloudSuite Industrial most reports are run from a report form, previewed in a viewer (for SSRS-based reports, rendered by SQL Server Reporting Services), then printed, saved to PDF or Excel, or e-mailed. Scheduling is done by running the same report as a background task, so it depends on the Task Manager service and on a printer or file destination the service account can reach.
Applies to: Infor SyteLine 9.x and CloudSuite Industrial (CSI) 10.x on premises and multi-tenant. Form names and options vary by release; check your own menu.
View, export and schedule a SyteLine report
- 1Open the report form from the menu (or type the report name in the form search) and fill in the selection criteria, such as date range, customer or order range.
- 2Choose the output: preview on screen, print, or file. Preview opens the report in the viewer so you can page through it before printing.
- 3From the viewer or output options, export to PDF, Excel or another supported format, or e-mail it if mail is configured for your site.
- 4To save the selection you use every month, store the report options (see the related page on saving report options) so the criteria load automatically.
- 5To schedule, run the report as a background task: set the task parameters, the output (printer, file or e-mail) and the recurrence in the Background Task Definitions area.
- 6Confirm the Task Manager / background processing service is running, then check Background Task History for status and the error text of failed runs.
- 7For SSRS-based reports, confirm the report server URL and credentials are configured and the report folder is deployed; test one report interactively first.
Two kinds of report, two failure surfaces
SyteLine has reports built in older technologies and reports delivered as SSRS (Reporting Services) definitions. The user experience is similar, but failures are not. An SSRS report fails because of the report server: wrong URL, expired credentials, a missing data source or a deployment that did not include the report. A classic report fails inside the application tier or the print path.
When a user says the viewer shows nothing or an error, the first question is whether the failure is in the selection (wrong criteria, no data), the render (SSRS) or the delivery (printer, file share, mail). Run the same report interactively with a narrow range. If it renders, the problem is delivery or scheduling, not the report.
How scheduling really works
There is no separate scheduler product to learn. A scheduled report is a background task: a task definition that points at the report, carries the parameter values, and is picked up by the background task processor on the schedule you set. The processor runs as a Windows service under a service account, not as you.
That matters for output. A printer you can see in your session may not exist for the service account. A file path on your laptop is not reachable from the server. Use a UNC share the service account can write to, or a printer installed for that account on the utility server, and test with a one-off run before setting a recurrence.
Export options and their limits
PDF is the safest export for anything that will be filed or sent to a customer because layout is fixed. Excel exports from a rendered report keep what the layout shows, which is often not what finance wants. For analysis, a query-based export or the Excel add-in against the underlying data is usually cleaner than exporting a formatted report.
In multi-tenant CSI you cannot reach the database directly, so custom reporting has to go through supported reporting paths. See the related page on reporting without direct SQL.
About the SOC report query
Searches such as infor syteline soc report are ambiguous. If you mean a service organization control (SOC) assurance report for Infor's hosted CloudSuite, that is a trust and compliance document obtained through Infor, not an in-application report. If you mean a shop order or operations report named SOC at your site, it is a customization and your administrator or partner owns its definition.
Common pitfalls
- !Scheduling with a printer or path that exists for you but not for the background service account.
- !Assuming a failed scheduled run will alert anyone; check Background Task History or set up an alert.
- !Exporting a formatted report to Excel for analysis instead of pulling the underlying data.
- !Testing only on a large date range, so a rendering timeout hides a deployment problem.
- !Changing the SSRS server or credentials and forgetting the scheduled tasks that depend on them.
How an ERP-grounded AI assistant handles this
Report viewers answer questions you already know how to ask. A grounded assistant such as SyteRay or ERPray can answer the ad hoc version, for example which customers shipped late last month, by running a read-only query over SyteLine data and showing the query and result, so users stop requesting one-off reports. Scheduled statutory or customer-facing reports should stay as governed SyteLine reports. For on-prem sites the model runs on your own GPUs, so data does not leave the network.
Frequently asked questions
Is there a separate report scheduler in SyteLine?
Not as a separate product. Scheduling is done by creating a background task for the report with parameters, output and recurrence. The Task Manager service executes it, so the service must be running and its account needs access to the output destination.
Why does a report preview work but the scheduled run fails?
Usually the context differs. Your session has your printer, your permissions and your shares. The background service account may not. Check Background Task History for the exact error and test with a file output to a share the service account can write to.
Can I export a SyteLine report to Excel?
Yes, where the output options offer it. The result reflects the report layout. For analysis, use a data-level export or the Excel add-in, which gives you clean columns instead of formatted pages.
Where do I configure SSRS for SyteLine?
In the reporting configuration of your environment, set during installation or by your administrator: the report server URL, credentials and deployed report folder. Changes there affect every SSRS report, so test after any change.
Related
How to Use Report Options and Print to PDF in SyteLine
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.
Error fixSyteLine 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 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.
Error fixSyteLine Background Tasks Stuck or Not Processing
Background tasks stall for four main reasons: the processor service is not running or points at the wrong configuration, a task is flagged Running from a crash and blocks its own next run, the account it runs as cannot log in, or the work is blocked in SQL. Check the processor first, then task status and history, then the run-as user, then SQL.
AdvancedReporting in CloudSuite Industrial Multi-Tenant Without Direct SQL Access
When a multi-tenant CloudSuite Industrial tenant does not expose its SQL Server, replace direct queries with three supported patterns: IDO-based reports and the IDO REST service for operational reads, Infor reporting tools for standard documents, and data lake extracts for analytics and history. Choose by freshness and volume: REST for small, current reads, the data lake for large, historical or cross-system analysis.
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.
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.
Keep exploring
ERP fixes and how-tos
- How to Use Report Options and Print to PDF in SyteLineHow to set SyteLine report selection criteria, save them, output to preview or PDF, run in the background and fix reports that return no data.
- How to Schedule a Background Task in SyteLine Task ManagerHow to schedule recurring background work in SyteLine Task Manager - MRP runs, reports, custom IDO methods - and why a task silently stops running.
- SyteLine Printers: Where to View Them and How They Map to Reports and Background TasksHow SyteLine / CSI finds printers, where to check what is available, and how to map printers to reports and background tasks without 'printer not found' surprises.
Guides
- SyteLine Background Task Development GuideBuild SyteLine background tasks. Task scheduler configuration, IDO method-based tasks, error handling, and monitoring for batch processing jobs.
- Fixing Slow SyteLine ReportsFix slow SyteLine reports by separating queue time from execution time, reading SSRS execution logs, tuning the dataset query, and scaling task processing.
- SyteLine Custom Report Development with SSRSBuild custom SSRS reports for SyteLine. Data sources, stored procedures, parameter mapping, deployment, and report server configuration guide.