Description/Symptoms
Custom 360Eyes reports are no longer functioning after a recent upgrade.
How to replicate the issue:
- Open the application and attempt to run a custom report that previously worked.
- Observe that the report fails to execute or returns incorrect data.
- The user notes that default reports may still function, but custom ones do not.
Cause
Custom reports are not officially supported by Wiiisdom. Major upgrades can introduce changes to the underlying data model (tables, columns, extraction logic) that may break custom reports. Since these reports are built for specific customer requirements and are not part of the standard offering, it is not possible to guarantee their compatibility with future releases or to notify in advance of all possible impacts.
Resolution
There are several steps and recommendations to address this situation:
Option 1: Validate in Development Before Production
- Always install new versions in your development environment first.
- Test your custom reports against the new version using a recent development snapshot.
- Compare results between the development and production environments to ensure consistency.
- If your custom reports work as expected in development, proceed to upgrade production.
- If issues persist, do not upgrade production and proceed to Option 2.
Option 2: Seek Support for Custom Reports
- If your custom reports do not work after following the above steps, contact the support team with detailed information about the issue.
- While custom reports are not officially supported, the team can provide guidance or suggest workarounds on a best-effort basis.
Option 3: Use Standard Reports
- Consider using or adapting the standard reports provided with the product, as these are maintained and tested for compatibility with each release.
- Note that standard reports are templates and may require customization to fit your needs, but their structure is more likely to remain compatible across versions.
Additional Information
- The support team does not guarantee compatibility or provide advance notice for custom report breakage, as the specifics of custom implementations are unknown.
- Major upgrades may introduce breaking changes; always validate in a non-production environment first.
- If you encounter a bug with standard reports or the universe, report it to support for resolution in future releases.
Summary of Support Position:
- Custom reports are not supported.
- Always validate with the latest version in development before moving to production.
- If your custom reports fail, contact support, but no guarantees can be made.
- Standard reports are maintained and should be used as a baseline.
If you need a more detailed troubleshooting guide or have specific questions about your custom reports, please provide the report details and the steps you have already taken. The support team will do their best to assist you.