Articles in this section
Category / Section

Why Bold BI Does Not Support Downgrading to a Previous Version?

Published:

Bold BI is a comprehensive business intelligence platform that offers powerful features and functionalities for creating and managing interactive dashboards and data visualizations. However, there are certain limitations and dependencies that prevent the downgrading of Bold BI to previous versions. This article discusses the reasons why downgrading Bold BI is not feasible.

Reverting DB Queries

When upgrading to a newer version of Bold BI, there may be changes in the underlying database schema and queries. These changes are often required to introduce new features, improve performance, or fix issues. Reverting to an older version would necessitate rolling back these database changes, which can be complex and may lead to data inconsistencies and errors.

Incompatible Dashboard Updates

Once the dashboard is updated in new version and attempting to downgrade to an older version could result in the loss of these updates or the inability to render the dashboards properly due to compatibility issues.

.NET Core Version Mismatch

Bold BI is built on the .NET Core framework, which provides the foundation for its functionality. As part of ensuring security, performance, and compatibility, Bold BI regularly upgrades its .NET Core versions in alignment with industry best practices. It is important to upgrade to the latest .NET Core version before the support for the existing version expires. Downgrading Bold BI would require rolling back the .NET Core version, which may lead to compatibility issues and potential security vulnerabilities.

Environment Specific Changes

Bold BI can be deployed in Windows, Linux, Kubernetes, Docker or Azure App Services. In some cases, there may be environment specific changes will be done in newer versions and reverting these changes will be difficult one.

Was this article useful?
Like
Dislike
Help us improve this page
Please provide feedback or comments
RK
Written by Ramesh Kannan Rajendran
Updated:
Comments (0)
Please  to leave a comment
Access denied
Access denied