A Sage Intelligence report can be perfectly designed and still stop working.
Start With Scope
Does one report fail or all of them? One user or everybody? Did it begin after a Sage upgrade, workstation change, server migration, licensing change, Office update, or permissions change?
The Environment Can Change Around the Report
Sage Intelligence lives in a real workstation and server environment. Access, licensing, Excel, Sage connectivity, paths, permissions, and upgrades can all affect the workflow.
Licensing Is More Visible in 2026
Sage announced that the Unlimited subscription option is going away under Sage 100 and Sage 300 subscription plans and access is moving to per-user billing. The capabilities did not change, but user access assumptions now matter more directly.
Upgrades Are a Natural Checkpoint
Run the reports people actually depend on. Refresh them. Drill down. Confirm the output and automated distribution.
Custom Reports Carry Business Logic
A custom report may contain years of account groupings, formulas, departmental presentation, and management expectations. Troubleshooting should protect that logic rather than casually rewriting it.
What We Check
- Who is affected
- Which reports are affected
- Whether Sage access is otherwise normal
- Whether licensing or permissions changed
- Whether Excel, Sage, the workstation, or server changed
- Whether the report still connects to the expected data
- Whether automated distribution still runs
- Whether the report itself was modified