Data Source Configuration and SyteLine Schema Access
SSRS reports for SyteLine use a shared data source pointing to the SyteLine application database. The connection string must reference the correct database instance and use Windows Authentication or SQL Authentication as configured during SyteLine installation. SyteLine's reporting views (vw_co_detail, vw_job_detail, vw_inv_detail) provide denormalized data optimized for reporting, though direct table access to SLCos, SLJobs, and SLItems is sometimes necessary for custom requirements.
- Configure shared data source in Report Manager pointing to the SyteLine SQL Server instance with proper credentials
- Use SyteLine reporting views (vw_co_detail, vw_job_detail) as primary data sources for standard reports
- Join SLCos, SLCoitems, SLCustomers, and SLCustaddr tables for custom order reports not covered by views
- Access SLItems, SLWhseitems, and SLItemwhse for inventory reports with warehouse-level detail
- Set CommandTimeout on the data source to 300 seconds minimum for reports querying large transaction tables
Parameter Design and SyteLine Context Integration
SyteLine passes context parameters to SSRS reports when launched from forms, customer number from the Customer form, job number from the Job Orders form, and date ranges from scheduling screens. Report parameters must match the names and data types that SyteLine's report launcher expects. Multi-value parameters for warehouse, site, or status filters require special handling in the WHERE clause using IN expressions.
- Define parameters matching SyteLine's report launcher expectations: @CoNum, @CustNum, @JobNum, @StartDate, @EndDate
- Use cascading parameters for site/warehouse filtering: @Site populates @Whse dropdown from SLWhse filtered by site
- Implement multi-value parameters with JOIN to a split function for IN clause filtering on status or type fields
- Set default parameter values from SyteLine session variables (site, warehouse, user) for one-click report execution
- Handle optional parameters with ISNULL or COALESCE in SQL to show all records when no filter value is provided
Report Deployment and SyteLine Integration
SSRS reports for SyteLine are deployed to the Report Server and registered in SyteLine's report catalog through the Forms and Reports administration. The report path in SyteLine's SLReports table must match the Report Server folder structure. After deployment, test the report from within SyteLine's UI to verify that context parameters pass correctly from the launching form to the embedded report viewer.
- Deploy .rdl files to the SSRS Report Server using Report Manager or Visual Studio deployment profiles
- Register the report in SyteLine's report catalog via the Report administration form with correct path and parameters
- Configure report subscriptions in SSRS for scheduled delivery via email or file share in PDF, Excel, or CSV format
- Test parameter passing by launching the report from the SyteLine form that will invoke it in production
- Set up report execution logging in SSRS to monitor run times and identify slow-performing reports for optimization
Try it here, free
SyteLine Database Tables Reference
Searchable lookup of the main SyteLine SQL tables, what each holds and its usual business key, for writing queries and reports.
Need custom SSRS reports for SyteLine? Netray's report development agents generate optimized reports from your specifications, get started.