0

I've got a lightning component that fires e.force:createRecord but can't get it to respect either the "Salesforce Classic Override" (VF page) or "Lightning Experience Override" on the New action.

The overrides work fine from Salesforce pages - lists, related lists, etc.

Has anyone gotten this to work? If so, how?

  • This event is handled by the one.app container. It’s supported in Lightning Experience, the Salesforce app, and Lightning communities. This event presents a standard page to create a record. That is, it doesn’t respect overrides on the object’s create action. – sanket kumar Sep 14 '18 at 7:07
0

hmmm.. wondering if this has something to do with it.

https://releasenotes.docs.salesforce.com/en-us/summer17/release-notes/rn_lightning_action_overrides.htm

'Action overrides aren’t supported in Lightning console apps, and are silently ignored when invoked. If a Lightning console app user triggers an action that has been overridden, they see the standard action instead. If they trigger the same action outside of a Lightning console app, they see the overridden action. This behavior can result in an inconsistent user experience, which you should warn users about. Also ensure that you meet your data validation requirements using triggers and validation rules, rather than code that only runs in the action override. This strategy ensures that your data is valid, whether it’s changed using a standard action or an action override.'

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.