Crystal Reports or SEI dashboards fail to run, return wrong data, or time out. Numbers don't match Sage X3 inquiries.
Crystal or SEI reports that fail, return wrong numbers, or don't match Sage X3 inquiries are usually pointing at a stale or removed table/view, have a parameter mismatch against the Sage X3 prompt definition, or — for SEI — haven't had the model refreshed after a Sage X3 patch. Start by running the report against a known transaction and tracing every field, since differences almost always come down to missing joins or status filters.
Why it happens
- Report points to a stale or removed table/view
- Parameter mismatch between Sage X3 and the report definition
- SEI model not refreshed after a Sage X3 patch
- Underlying query lacking necessary joins or filters
- Database user lacking access to a referenced object
Diagnostic steps
- 1. Run the report against a known dataset
Pick a known transaction and trace every field. Differences are usually missing joins or status filters.
- 2. Check parameter binding
Crystal parameters must align with Sage X3 prompt definitions. A mismatch often returns no data instead of an error.
- 3. Refresh the SEI model
After Sage X3 patches, refresh the SEI metadata layer so structural changes flow through.
- 4. Confirm database permissions
Report user needs SELECT on every object referenced — including new views from patches.
Fixes
Rebuild the underlying query
Replace ad-hoc Crystal SQL with a Sage X3 inquiry or SEI model so future changes propagate.
Standardize parameters
Use Sage X3 print code parameters consistently across reports for predictability.
Establish a report register
List every custom report, its owner, and its data source. Reports without owners get deprecated.
Move executive reporting to SEI
SEI is generally a better fit than Crystal for financial and executive reporting.
Prevention
- Report regression tested with every Sage X3 patch
- Report register reviewed annually
- Standards for query design and parameter handling
PRH Consulting can resolve this for you
Our reporting & bi practice handles issues like this regularly. Most engagements start with a short scoping call.