[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["難以理解","hardToUnderstand","thumb-down"],["資訊或程式碼範例有誤","incorrectInformationOrSampleCode","thumb-down"],["缺少我需要的資訊/範例","missingTheInformationSamplesINeed","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間：2025-09-05 (世界標準時間)。"],[],[],null,["# Admin settings - Legacy features\n\n| **Note:** [Looker (Google Cloud core)](/looker/docs/looker-core-overview) instances don't include this page.\n| **Note:** If you have a permission that provides access to only select pages in the Admin panel, such as [`manage_schedules`](/looker/docs/admin-panel-users-roles#manage_schedules), [`manage_themes`](/looker/docs/admin-panel-users-roles#manage_themes), or [`see_admin`](/looker/docs/admin-panel-users-roles#see_admin), but you don't have the [Admin role](/looker/docs/admin-panel-users-roles#default_roles), the page or pages that are described here may not be visible to you in the Admin panel.\n\nLooker will occasionally make updates to product design and functionality that render an existing feature's functionality obsolete. In some cases, the feature may be designated as a *legacy* feature --- a feature that remains backward compatible for existing workflows. A legacy feature provides the option for existing users to continue to use the feature's functionality. When a legacy feature is enabled, the Looker instance cannot support the old and new functionality simultaneously.\n\nAfter you [learn about a new legacy feature](#learning_about_new_legacy_features), you should start planning to [migrate to the new functionality](#migrating_away_from_legacy_features) before you [disable the legacy feature](#enabling_and_disabling_legacy_features).\n\nSee the [Legacy feature schedule](#legacy_feature_schedule) section on this page for version information about when each legacy feature is introduced, disabled, and removed from Looker.\n\nLearning about new legacy features\n----------------------------------\n\nLooker announces new legacy features in the release notes. See the [Looker releases](/looker/docs/looker-releases) page for links to the release notes for the latest Looker release.\n\nThe [Current legacy features](#current_legacy_features) section later on this page provides a timeline showing when current legacy features will be disabled and formally removed from the Looker product. See the [Previously removed legacy features](#previously_removed_legacy_features) table on this page for Information about legacy features that have already been removed from Looker.\n\nEnabling and disabling legacy features\n--------------------------------------\n\nNew features that replace legacy features are often simpler, more reliable, more performant, and/or more useful than the features they replace. To take advantage of the improved functionality of a new feature that replaces a legacy feature, migrate away from the legacy feature. Once that transition is complete, a Looker admin can disable the legacy feature on the [Legacy Features](/looker/docs/legacy-features#enabling_and_disabling_legacy_features) page in the **Admin** panel.\n\nThe **Legacy Features** page appears in the **Admin** panel only if there are legacy features available for that Looker instance. The number located next to the **Legacy Features** admin menu item indicates the number of legacy features that are enabled.\n\nWhen Looker is updated, some legacy features are enabled by default, which means that the old feature is still active. When you're ready to move to the new feature, you can turn the legacy feature off.\n\u003e If your Looker instance is created after a legacy feature is [disallowed](#legacy_feature_schedule), that feature won't appear on the **Legacy Features** page, and admins won't be able to turn it on. The **Legacy Features** page won't appear in the **Admin** panel if there are no legacy features available to your instance for your current Looker version.\n\u003e\n\u003e If you update your existing Looker instance to a version in which a legacy feature is disabled by default, your instance will use the new feature behavior automatically.\n\nMigrating away from legacy features\n-----------------------------------\n\nEventually, all legacy features are removed from Looker, so Looker strongly recommends moving away from their use. Start planning your migration as early as possible to avoid disruptions to your workflows.\n\n### Planning your migration\n\nLooker announces new legacy features in the [release notes](/looker/docs/looker-22-release-highlights). When needed, Looker provides transition guidelines for migrating away from legacy features. The [Legacy feature schedule](#legacy_feature_schedule) on this page provides a timeline that shows when current legacy features have been or will be formally removed from the Looker product. The schedule also notes when the features will be disabled by default.\n\nLeave the legacy feature enabled while you implement any necessary transition guidelines. Once these guidelines have been implemented, disable the legacy feature. Be mindful of migrating away from the legacy feature before updating your Looker instance to the version in which the legacy feature is disabled by default. If you have any issues implementing the improved replacement feature, [open a support request](http://console.cloud.google.com/support/cases).\n\nLegacy feature schedule\n-----------------------\n\n- **Introduced** indicates the version or date in which the feature becomes a legacy feature and appears in the **Legacy Features** page in the **Admin** panel.\n- **Disabled** indicates the version or date in which the legacy feature is turned off for all instances that update to the release. The legacy feature toggle remains available in the **Legacy Features** page for the purposes of remediation, if required.\n- **Disallowed** indicates the version or date in which the legacy feature is removed from the **Legacy Features** page for newly created Looker instances. If you update your existing Looker instance to this version, the legacy feature toggle remains available.\n- **Removed** indicates the version or date in which the legacy feature is removed from the **Legacy Features** page for all Looker instances.\n\n### Current legacy features\n\n### Previously removed legacy features"]]
