# SyteLine Report Viewer: Preview, Export and Schedule Reports (SSRS and Background Tasks) > Source: https://netray.co/erp-help/syteline-report-viewer-schedule-export-ssrs > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## 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. ## Kind how-to ## System syteline ## Erp Infor SyteLine (CloudSuite Industrial) ## Module Reporting / SSRS / Background Tasks ## Query syteline report viewer ## Alternate Queries - infor csd report scheduler - sightline reporting - infor syteline soc report ## 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. ## Steps ### View, export and schedule a SyteLine report **Items:** - Open 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. - Choose the output: preview on screen, print, or file. Preview opens the report in the viewer so you can page through it before printing. - From the viewer or output options, export to PDF, Excel or another supported format, or e-mail it if mail is configured for your site. - To save the selection you use every month, store the report options (see the related page on saving report options) so the criteria load automatically. - To 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. - Confirm the Task Manager / background processing service is running, then check Background Task History for status and the error text of failed runs. - For SSRS-based reports, confirm the report server URL and credentials are configured and the report folder is deployed; test one report interactively first. ## Sections ### Two kinds of report, two failure surfaces **Body:** 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 **Body:** 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 **Body:** 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 **Body:** 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. ## 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. ## Ai Angle 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. ## Faq ### Is there a separate report scheduler in SyteLine? **Answer:** 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? **Answer:** 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? **Answer:** 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? **Answer:** 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. ## Search terms syteline report viewer, syteline report scheduler, infor csi report scheduler, syteline ssrs reports, syteline export report to pdf, syteline background task report, sightline reporting, infor syteline reports, syteline soc report --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json