Apex Code Development You need to sign in to do that
Don't have an account?
CarlB Summer 17 Lightning/VF bug with record types
Hello.
I was wondering if anyone else had come across this problem with the latest release. I have a custom object which has a lookup field to Contact and some record types. I have created a VF page that overrides the standard "New" action for this object. In classic Salesforce, if I go to a Contact and create a new instance of my custom object from the related list, the lookup field in that object is automatically populated with the Contact. However, if I switch to Lightning, there are two issues. Firstly, the standard record type selection screen is incorrectly formatted (I suspect a missing CSS file). Secondly (and more importantly), the lookup field is no longer populated.
It seems that during the update, Salesforce have changed something which means that Lightning is no longer backwardly compatible with VF.
Has anyone else encountered this and is there a work-around?
Regards,
Carl
I was wondering if anyone else had come across this problem with the latest release. I have a custom object which has a lookup field to Contact and some record types. I have created a VF page that overrides the standard "New" action for this object. In classic Salesforce, if I go to a Contact and create a new instance of my custom object from the related list, the lookup field in that object is automatically populated with the Contact. However, if I switch to Lightning, there are two issues. Firstly, the standard record type selection screen is incorrectly formatted (I suspect a missing CSS file). Secondly (and more importantly), the lookup field is no longer populated.
It seems that during the update, Salesforce have changed something which means that Lightning is no longer backwardly compatible with VF.
Has anyone else encountered this and is there a work-around?
Regards,
Carl