Cloud
Reporting in CloudSuite Industrial cloud without direct SQL: what to use instead
Applies to: Teams moving from on-premises SyteLine to multi-tenant CloudSuite Industrial, or already there. Exact features depend on your release and subscription
Short answer
In multi-tenant CloudSuite Industrial you can't connect to the database with SQL, so anything that reads tables directly, such as SQL-based reports, Excel ODBC links and BI tools pointed at the database, has to move. The replacements depend on the job: DataViews for lists people filter and export, Report-type forms for fixed-layout documents (Infor's recommended route for new reports, with SSRS now deprecated), standard reports wherever they already do the job, the IDO REST API through the ION API gateway for integrations and small live reads, and the Infor Data Lake for history and analytics. Inventory every direct-SQL consumer before the move, not after.
What stops working
On-premises, many sites have grown reporting habits that all rely on reading the database directly:
- Custom SSRS or Crystal reports with their own SQL or stored procedures
- Excel workbooks with ODBC connections to the SyteLine database
- Power BI or other BI tools pointed at SyteLine tables or views
- SQL Agent jobs that export data to files for other systems
- "Quick" ad hoc queries run in SQL Server Management Studio
None of these have a database to connect to in multi-tenant cloud. In single-tenant or hosted setups the rules can differ, so confirm what your agreement includes.
What replaces what
| Old habit | Cloud replacement | Notes |
|---|---|---|
| Lists and lookups exported to Excel | DataViews | Users filter, group, total and export themselves. Covers most "can I get a list of..." requests |
| Fixed-layout documents and scheduled reports | Report-type forms, or a modified copy of a standard report | Infor's documentation describes Report-type forms as the recommended route for new reports, with custom SSRS still supported but deprecated |
| Integrations and small live reads | IDO REST API via the ION API gateway (how it works) | Goes through SyteLine's business logic and security. Fine for current data in reasonable volumes, slow for big multi-table extracts |
| History, trends, cross-system analysis | Infor Data Lake, queried with Infor's tools, or fed to your BI tool | Not live: it reflects the last time data was sent to the lake |
| Dashboards | DataView-based drilldowns, or BI over the Data Lake | Depends on your subscription |
The question to ask for each report is the same as on-premises: is it a list, a document, or analysis? See DataViews vs SSRS vs Crystal.
Inventory before you move
- List every direct-SQL consumer. Custom reports and their stored procedures, Excel files with ODBC connections, BI tools, SQL Agent jobs, exports. Your DBA can list logins and recent connections to the SyteLine database. Ask the business for the spreadsheets that matter at month-end.
- Record who uses each one and how often. Unused ones are retired, not rebuilt.
- Check for a standard replacement. A standard report or DataView may already cover it.
- Decide the route for the rest: DataView, Report-type form, API, or Data Lake.
- Estimate and schedule the rebuild before go-live. Month-end reports first.
- Test with real data and sign off against the old output, as you would for any report migration. See Converting Crystal Reports to SSRS for the comparison method.
Common traps
- Pulling big extracts through the API. The IDO REST API is built for operational reads. For years of history, use the Data Lake.
- Expecting live data from the lake. Plan dashboards around how often data is sent there.
- Rebuilding everything as a report. Most "reports" in an old library are lists that work better as DataViews.
- Forgetting the spreadsheets. The Excel files with database connections are usually the last thing anyone remembers, and the first thing finance misses.
Custom logic you still need
If a report needs a calculation that doesn't exist as an IDO property, it can often be added through supported customization, such as a custom IDO method or a calculated property, within what multi-tenant allows. Plan that work with whoever manages your customizations, and keep it as small as possible, because every customization has to be carried through future releases.
FAQ
Can I use SQL with CloudSuite Industrial multi-tenant?
Not directly against the database. Data is reached through IDOs: DataViews, reports, the IDO REST API and, for analytics, the Infor Data Lake.
What replaces custom SSRS reports in CloudSuite Industrial?
Infor recommends Report-type forms or DataView-based reports for new work. Custom SSRS is still supported but deprecated. Check whether a standard report already does the job first.
How do I get SyteLine cloud data into Power BI?
Usually through the Infor Data Lake for history, or the IDO REST API for small, current datasets. Direct database connections aren't available in multi-tenant.
What should I do before moving SyteLine reports to the cloud?
Inventory every report, spreadsheet, BI connection and job that reads the database directly, retire what's unused, and plan a replacement for the rest before go-live.