Moving to Syteline 10 (CSI) - what is used for custom report creation

Syteline has been through a bit of change for reporting 8.02 and below, Crystal reports, 8.03 Sql Server Reporting, etc.

What does Syteline 10 (Cloud Suite Industrial) use for reporting? I will need to convert our custom reports to the new reporting tool(s).

thanks.

Find more posts tagged with

FAQs, How-To, and Best Practices

Accepted answers

All comments

kazuyuki mochizuki

Hello,

In CSI10 it uses ReportViewers, try and open any form that has "reportviewer" in its name and have a look.

There's also instructor led trainings available in Infor Campus.

Regards,

Kaz

Joe Ueberroth

Are you going to 10 on Prem. If so, my understanding is that you will still have SSRS reporting capability but most reports are being evolved to the Flex Form (Report) Tool. We are on Cloud, so all our reporting is done with Flex Form Reports.

If you're going to Infor Cloud Hosted, you will be using the Runtime Bulder / Form Builder / Report wizard to generate new reports and their corresponding criteria forms. It's actually very slick and has come a long way since its inception. The Flex Layout Form Reports are a different animal than SSRS and will take some practice. As Kaz said, the OOB (existing) Reports (Flex Forms) end in the name 'Viewer'. You cannot open these directly. You need to use Form / Definition / Designer or open the Win Studio Web Interface using the Designer icon, then open a Viewer form there in design mode to work with it. When creating a new report with the wizard, the Report Wizard does not force that 'Viewer' naming convention on you for the resulting report name. I would recommend you end your report name with 'Viewer' for conformity.

As Kaz indicated there are good instructor Led courses thru Infor U.

I would highly recommend you get the Demo database up first and take the instructor led courses in Infor U and play with Flex Forms.

Good luck.

Joe

Darryl Hoar

We are going to be on Prem. Where are the report files located on the filesystem? We are going to be running the webclient, so I guess I'll edit from there as I saw no stand alone Form/definition/designer tool installed.

SXFlagMan

SL 10 uses Mongoose Reporting. The reports (usually suffixed with the word viewer) are now a version of a mongoose form. You modify and create them in SL. They can be exported using FormSync, which is also now in Syteline as its own form.

Joe Ueberroth

Hi Darryl:

The Web client's 'Designer' is the Win Studios web version. For the most part its very similar to fat client Win Studio.

Accessing this Win Studio Designer can be accomplished using the pull-down menus Form, then Definition, Then Designer. (If you have 'Layout/Toolbar Type/Standard' chosen as your layout in user preferences) Or using the Icon for the designer. From there you can open the forms. To look at existing reports use the word viewer in the Open Dialogue filter prompt. You can't open these forms directly from the Form Open Dialog outside designer. Ive copied in some notes I gathered below on 'Why'.

There really are no 'Report Files' as it petain to non SSRS reports. Aghain you will have access to your SSMS reports after conversion. You may need to start using the new Flex Form versions to incorporate the changes in the new version of Syteline for some of your older reports.

The 'New' reports are really just specially designed forms. Yyou use Runtime Bulder / Form Builder / Report wizard to generate new reports that use a report template (set of properties) for a Report type output. I believe without the pull down menus you can run the wizards from form open.

With some work, you could create a report and manually build a criteria form to generate a report.

The Data View Wizard is pretty slick also. It is another choice off of the Runtime Builder.

Again, I highly recommend Infor Classes as Kaz suggested in the initial response.

Why `…Viewer` forms don’t open from the Form Open dialog

They’re “Report Type” (template) forms, not runtime UI.
In Mongoose Reporting, the report layout lives in a special Report Type form. These are real Mongoose forms, but they behave differently from normal runtime forms. The normal pattern is: Criteria form → background task → Viewer. You don’t launch the Viewer by hand; the report engine opens it with the parameters and data it needs.
Web client limitation for templates/runtime preview.
In the web client (which Cloud uses), you can view the template, but you can’t use the runtime preview or generate the report directly from the template. That’s by design—generation happens through the criteria and task pipeline, which then invokes the Viewer.
Many Viewers are deployed as “internal-use” forms.
Vendors commonly ship Viewer/Report Type forms with properties like Hidden, Allow Runtime = No, or a specific Category so they’re not discoverable in the Form Open dialog. They’re opened programmatically with the correct context (parameters, data view, rendering). This pattern is part of the move to Mongoose Reporting for Cloud tenants.
“Viewer” naming is a reporting convention.
The shift to Mongoose Reporting in SL/CSI means reports are packaged as forms (often suffixed Viewer), modified and moved via FormSync, and opened by the reporting flow—not directly by users.

How to run or work with those reports

Use the associated Criteria form (recommended).
Find and open the related …Report or …Criteria form (naming varies by report). Supply parameters, then Run (foreground) or Submit (background). The system will generate the output and open the corresponding …Viewer automatically with the right data.
Run as a background task from the Criteria form or Report menu.
In Cloud, reports typically run as background tasks. When the task finishes, the Viewer opens or the output is available to view. This avoids the web client preview limitations mentioned above.
Design‑time access (for developers).
If you need to inspect or edit a Viewer/template:
- Open the form in Design Mode in a dev/sandbox tenant (with Workbench privileges).
- Review components (layout, DataViews, parameters, events).
- Avoid changing Hidden/Allow Runtime flags in production; that can break the report flow and upgrade compatibility.

Good Luck,

Joe

Copyright © 2025 Infor. All rights reserved.