Common Issues and Solutions with Reporting and Using Report Builder

When troubleshooting issues in ReadyWorks Report Builder, it's important to approach the problem systematically. Here are some common issues you may encounter, along with strategies for resolving them:

1 - Report fails to load or loads incompletely:

This issue often relates to data volume or complexity.

• Check the report's data source and filters:
  • Ensure that the primary data source is appropriate for the report's purpose.
  • Verify that global WHERE clauses and filters are not overly restrictive.
• Review calculated columns:
  • Look for complex calculations that might be causing performance issues.
  • Consider simplifying calculations or pre-calculating values where possible.
• Examine linked asset data:
  • Reduce the number of fields pulled from linked assets if not all are necessary.
• Consult with your ReadyWorks administrator:
  • They may need to optimize database indexes or increase server resources.

2 – Inconsistent or unexpected data:

When report data doesn’t match expectations, consider these steps:

• Verify data refresh timing:
  • Check when the last data import occurred.
  • Ensure that refresh rates are appropriate for the data’s volatility.
• Cross-check with source systems:
  • Compare a sample of data points with the original data sources.
  • Look for any discrepancies in data mapping or transformation.
• Review calculation logic:
  • Double-check the formulas used in calculated columns.
  • Ensure that RAG status criteria are correctly defined.
• Examine filters and WHERE clauses:
  • Verify that filters are not inadvertently excluding relevant data.
  • Check for any conflicting filter conditions.

3 - Action buttons or forms not working as expected:

If interactive elements are malfunctioning:

• Check user permissions:
  • Ensure that users have the necessary rights to perform the actions.
  • Verify that the report itself has the correct permissions set.
• Review action button configuration:
  • Check the action button's script for errors.
  • Ensure that any conditions for button activation are correctly set.
• Test form functionality:
  • Verify that all form fields are correctly mapped to asset attributes.
  • Check for any validation rules that might be preventing form submission.

4 - Report performance degradation over time:

If a previously well-performing report becomes slow:

• Analyze recent changes:
  • Review any modifications made to the report structure or calculations.
  • Check if data volume has significantly increased recently.
• Examine usage patterns:
  • Look for an increase in concurrent users or frequency of report runs.
  • Consider implementing staggered refresh times for heavy reports.
• Consult system logs:
  • Work with your ReadyWorks administrator to review system logs for any anomalies.
  • Look for patterns in when performance issues occur.

5 - Discrepancies between preview and published report:

If the preview doesn't match the published version:

• Check for unsaved changes:
  • Ensure all modifications have been saved before publishing.
  • Re-publish the report if necessary.
• Review user-specific settings:
  • Verify if any discrepancies are due to user-specific filters or permissions.
• Clear cache and cookies:
  • Instruct users to clear their browser cache and cookies.
  • Test the report in an incognito/private browsing window.

When troubleshooting, always approach the problem methodically:

1. Clearly define the issue.
2. Gather relevant information (error messages, affected users, recent changes).
3. Test in a controlled environment if possible.
4. Apply potential solutions one at a time, testing after each change.
5. Document the problem and solution for future reference.