Infor SyteLine3 min readNetray Engineering TeamUpdated March 4, 2025

How to Configure Crystal Reports in SyteLine

Crystal Reports has been a long-standing reporting solution integrated with SyteLine for creating pixel-perfect formatted documents and complex analytical reports. Configuring Crystal Reports properly within SyteLine requires setting up ODBC connections, mapping IDO data sources, and deploying report files to the correct server directories. This guide covers the complete configuration process from initial setup through production deployment.

Configuring ODBC and Database Connections

Crystal Reports connects to SyteLine data through ODBC data sources or direct OLE DB connections to the SQL Server database. Create a System DSN on the report server pointing to your SyteLine database using SQL Server Native Client 11.0 or later. Configure the connection with Windows Authentication or SQL authentication depending on your security model. Test the connection by verifying access to key tables like item_mst, coitem_mst, and job_mst. For multi-site environments, create separate DSNs for each SyteLine database to enable consolidated reporting.

Create System DSN using SQL Server Native Client 11.0 pointing to the SyteLine database server
Configure authentication matching your SyteLine security model, preferring Windows Authentication
Test connectivity by querying core tables like item_mst, coitem_mst, and job_mst
For multi-site setups, create individual DSNs per database and use sub-reports for consolidation

Designing Crystal Reports with SyteLine Data

Open Crystal Reports Designer and create a new report using the SyteLine ODBC connection as your data source. Select from SyteLine views like vw_CustomerOrder, vw_ItemWhse, or vw_JobMaterial for pre-joined datasets that simplify report design. Add parameter fields that map to SyteLine form filter values, allowing users to pass context from SyteLine forms directly to Crystal Reports. Use the Formula Workshop to create calculated fields for derived metrics like margin percentages, days-on-hand calculations, and aging buckets that SyteLine does not store natively.

Use SyteLine database views like vw_CustomerOrder and vw_ItemWhse for pre-optimized data access
Map Crystal Reports parameters to SyteLine form context variables for seamless integration
Build formula fields for calculated metrics like gross margin percentage and inventory turns
Implement sub-reports for detail drill-downs linking parent records to transaction history

Deploying Crystal Reports to SyteLine

Deploy completed Crystal Reports RPT files to the SyteLine report server directory, typically located at the configured ReportPath in the application configuration. Register the report in SyteLine using the Report Administration (RSAdmin) form by creating a new report entry with the RPT filename and parameter mappings. Configure the Crystal Reports runtime engine on the report server, ensuring the correct version of SAP Crystal Reports Runtime is installed matching your RPT file version. Test deployment by running the report from the SyteLine client with various parameter combinations.

Copy RPT files to the SyteLine ReportPath directory configured in the utility configuration form
Register reports in RSAdmin with correct parameter names matching Crystal Reports parameter fields
Install SAP Crystal Reports Runtime 13.0.x or later on the report server for production execution
Validate deployment by testing with minimum, maximum, and boundary parameter values

Frequently Asked Questions

Which version of Crystal Reports works with SyteLine?

SyteLine supports Crystal Reports versions 2013 and later, with Crystal Reports 2020 being the current recommended version. The report server requires SAP Crystal Reports Runtime matching your RPT file version. Most SyteLine 10.x implementations use Crystal Reports 2016 SP4 or later, supporting up to 256 concurrent report sessions per server instance.

Can Crystal Reports use SyteLine IDOs as data sources?

Crystal Reports cannot directly consume IDOs as data sources. Instead, it connects through ODBC or OLE DB to the underlying SQL Server database. However, you can create SQL views that mirror IDO property collections, giving Crystal Reports access to the same calculated fields and joined datasets that IDOs provide. This approach typically involves creating 5-15 custom views per reporting area.

How do I handle Crystal Reports performance issues with large SyteLine datasets?

Optimize Crystal Reports performance by using SQL Server views with proper indexing instead of direct table access. Add record selection formulas that push filtering to the database server rather than applying them client-side. For datasets exceeding 100,000 rows, implement pagination or summary-level reporting. Enable report caching on the Crystal Reports server to avoid re-executing unchanged reports within a 30-60 minute window.

Key Takeaways

1Configuring ODBC and Database Connections: Crystal Reports connects to SyteLine data through ODBC data sources or direct OLE DB connections to the SQL Server database. Create a System DSN on the report server pointing to your SyteLine database using SQL Server Native Client 11.0 or later.
2Designing Crystal Reports with SyteLine Data: Open Crystal Reports Designer and create a new report using the SyteLine ODBC connection as your data source. Select from SyteLine views like vw_CustomerOrder, vw_ItemWhse, or vw_JobMaterial for pre-joined datasets that simplify report design.
3Deploying Crystal Reports to SyteLine: Deploy completed Crystal Reports RPT files to the SyteLine report server directory, typically located at the configured ReportPath in the application configuration. Register the report in SyteLine using the Report Administration (RSAdmin) form by creating a new report entry with the RPT filename and parameter mappings.

Struggling with Crystal Reports integration in SyteLine? Netray's reporting specialists can configure and optimize your Crystal Reports environment.

Talk to an Expert See a Demo

Related Resources

Infor SyteLine