Sign Up for Training |
Jet Global Company Site
Submit a Request
Give Feedback

Feature Deprecation In JDM 17.5

Some features in the Jet Data Manager have lived out their usefulness and continue to exist in the product solely for backwards compatibility. While backwards compatibility is high priority for us,developing and testing for outdated features takes time that we could otherwise spend on new useful features. For this reason we have created a process for feature deprecation and will begin marking features as deprecated in the product.

In the new release you will find a new setting, Deprecated Features, in the view menu:

When this is enabled, deprecated features are shown and can be used but will have “(deprecated)” added to their names to show you that they should no longer be used. The setting is disabled in new projects and enabled for old projects that use one of the deprecated features.

When a feature is put on the deprecated list we strongly recommend that you do not use the feature in new development. It will not stop working over night but at some point we will remove it from the product.
The feature deprecation process consists of three steps:


The feature is marked as deprecated in the software and is hidden by default in new projects.



If your project uses the deprecated feature, you will be warned that you should refactor your project to use a newer and better alternative. When possible, we will create automatic up-grade tools.



The feature is removed from the product and you will get an error message if try to open projects and project versions that use the feature.

The amount of time from a feature is marked as deprecated and until it is removed will depend on the feature. We will move features with an automatic upgrade option or low usage faster than features with high usage or features that take more time to remove from a project.

This release deprecates the following features and settings:

• Time tables. They have been replaced by date tables.

• On tables in the data warehouse: Data aggregations. Use an aggregated table instead.

• On staging databases: Data mapping. There are many better ways to do this in newer versions of the Jet Data Manager.

• On field-to-field data movement operations: Split and concatenate. A custom transformation is a better way to this.

• On conditional lookup fields: Force sub select, Use temporary table and SQL mode. The new algorithm introduced in this version does not make use of these settings.

Was this article helpful?
1 out of 1 found this helpful
Have more questions? Submit a request