Looker periodically deprecates certain product features. In some cases we provide a related “legacy feature” option, which allows you to continue using the deprecated feature while you implement a migration plan to improved functionality.
Looker brings you new features at a rapid pace. Sometimes we create a new feature, or make an improvement, that could be a breaking change and cause problems in your workflow.
To avoid such problems, we have the concept of Legacy Features — features that remain for backwards compatibility with your existing workflows. These legacy features eventually go away, but the legacy features enable you to update Looker and then migrate away from the old functionality at your own pace.
Learning about Deprecations
Watch the release notes to be notified that we are deprecating a feature, including features that we are still supporting as legacy features. The legacy feature deprecation schedule lists timelines for deprecated features that will eventually be fully removed from the product.
Enabling and Disabling Legacy Features
Admins have access to the Legacy Features page in the General section of the Admin menu, where features that have been phased out can be turned on and off. The Legacy Features option appears in the Admin menu and Admin page only if there are legacy features available for your instance.
The list of available features may vary, so the feature names and descriptions are blurred in this example:
The number located next to the Legacy Features menu item indicates the number of legacy features that are enabled.
When Looker is updated, any relevant legacy features are automatically turned on. This means the old feature is still active. When you’re ready to move to the new feature, you can turn the legacy feature off.
If your company started using Looker after a feature was deprecated, that feature won’t appear in the Legacy Feature panel and you won’t be able to turn it on. This prevents you from accidentally using features we have deprecated. The Legacy Feature panel won’t appear at all if there are no legacy features available to your instance for your current Looker release.
Migrating away from Legacy Features
Legacy features are features we plan on removing in the future, so we strongly recommend moving away from their use. Legacy features can often be confusing or inconsistent, which is why they’ve been replaced with something we think works much better.
As shown above, the Legacy Features panel displays each available legacy feature and the planned timing for removing that feature.
Start Planning Your Migration When a Feature Is Deprecated
We announce deprecations in the release notes. When Looker deprecates a feature, we provide information about what to do instead. You can also look at the full list of deprecations to help you plan your migration away from the deprecated features. That article also provides an end-of-life schedule, and information about how to transition away from the deprecated features.
You should expect that all legacy features will be turned off eventually. Thus, we recommend checking whether you are using the feature. If you are using it, leave the legacy feature enabled while you change your code. After you have completed the migration you can turn off the legacy feature.
Replacing a Legacy Feature
Almost all legacy features include some type of replacement functionality. If you have any issues implementing the improved replacement feature, please open a support request in Looker’s Help Center by clicking Contact Us.