We'd like to turn on Lightning in one of our full sandboxes, without turning it on in production. However, we want to understand the impact this would have on our ability to deploy from a QA Sandbox (with Lightning Enabled) to a Production environment (without Lightning enabled). Are there risks here, e.g. profile or other configuration changes, that would have to be manually deployed if Lightning is not consistently enabled across all environments? What other risks are there to turning Lightning on in one of our sandboxes from a developer point of view?
3 Kommentare
The only thing I can think of is similar to what @Michael Lupino mentioned, which is accidentally deploying changes to user profiles with Lightning enabled and inadvertently giving those profiles access to Lightning in production - but that wouldn't have any impact unless you also have Lightning "on" in Production first. You could use a separate sandbox for Lightning exploration, or if you need Lightning enabled in your main sandbox, then I would enable it in a limited fashion, just for admins/devs in that sandbox. For extra piece of mind, you could test customizations before deployment with a Classic only user in the sandbox.
