Confused about Visualforce standard button override and lightning.
We have many custom objects that have visualforce override for View, Edit and New buttons.
In lightning we can use standard LEX pages instead of visualforce pages. But given the user migration will happen in phases we want to keep some of the visualforce override until all users are migrated from classic.
It appears that for the view page following setting achieves that, keep the view button override but dont check the "Available in lightning and mobile" checkbox in the visualforce page settings. View page appears as visualforce in classic and LEX page in lightning.
But for Edit button, if the button is overriden in classic with a visualforce page then edit button cant even be added to the LEX layout in lightning. Is there a out of the box solution to keep the edit page as visualforce in classic and LEX pages in lightning without writing a lightning component?
@Jay Kanchana - Unfortunately, it doesn't look like it is possible to have an override in Classic and no override in LEX. We had it confirmed by Salesforce Support and the product manager. It would be seriously great if it was an option, though. Afterall, the greater flexibility of LEX often means that overrides that we needed in Classic aren't desireable any more.
In the end, we're thinking about usgin a generic "Edit" override LEX component which opens up the Edit modal pop-up for the record. However, that does mean that, in LEX, you can't use the in-line editing, which is a real shame. If you'd like me to share the generic Edit override component, I can PM you or just add it in an attachment here?
