{"id":6021,"date":"2017-05-08T17:50:34","date_gmt":"2017-05-08T17:50:34","guid":{"rendered":"http:\/\/www.jitendrazaa.com\/blog\/?p=6021"},"modified":"2017-05-22T19:19:41","modified_gmt":"2017-05-22T19:19:41","slug":"behold-yourself-summer-17-is-here-to-break-legacy-visualforce-navigation-code","status":"publish","type":"post","link":"https:\/\/www.jitendrazaa.com\/blog\/salesforce\/behold-yourself-summer-17-is-here-to-break-legacy-visualforce-navigation-code\/","title":{"rendered":"Behold Yourself – Summer 17 is here to break legacy Visualforce Navigation code in Lightning Experience"},"content":{"rendered":"

You read it right. Its not Locker Service<\/a> that may break your code, but Summer 17<\/a>. If you have legacy Visualforce page, which needs to navigate to Lightning experience and URLFOR<\/a> is used directly<\/strong>, then chances of getting below error are very high.<\/p>\n

\"Salesforce<\/a>
Salesforce Summer 17 – URLFOR Not working<\/figcaption><\/figure>\n

In above screenshot, I got\u00a0MALFORMED_ID : malformed Id\u00a0<\/strong>error in one of my Visualforce, where I needed to navigate to new Account record.<\/p>\n

Steps to reproduce error<\/strong><\/p>\n

Create below Visualforce in Summer 17<\/a>, where Lightning experience is enabled.<\/p>\n

DemoURLFor.vfp<\/span><\/p>\n

\r\n  <apex:page standardController="Account">\r\n Redirect Using URLFOR : <a href="{!URLFOR($Action.Account.New, null, [retURL='\/001',nooverride='1'], true)}">\r\n URLFOR - Not working in Summer 17 Lightning Experience <\/a> <br \/><br \/>\r\n Simple Redirect : <a href="\/001\/e?retURL=%2F001%2Fo&nooverride=1">Direct - Not working in Summer 17 Experience<\/a> <br \/><br \/>\r\n\r\n Working Example : <a href="javascript:createAccount()">Working with Summer 17 Experience<\/a> \r\n \r\n <script type="text\/javascript">\r\n function createAccount(){\r\n if( (typeof sforce != 'undefined') && sforce && (!!sforce.one) ) { \r\n sforce.one.createRecord('Account',null,{'retURL':'\/001','nooverride':'1'});\r\n }else{\r\n window.location='{!URLFOR($Action.Account.New, null, [retURL='\/001',nooverride='1'], true)}';\r\n }\r\n } \r\n <\/script>\r\n<\/apex:page>\r\n<\/pre>\n
Next step is to override New button<\/strong> of Account by above Visualforce page.<\/p>\n
After this setup, if we try to create New Account, below page will appear.<\/p>\n
\"Override<\/a>
Override New button in Salesforce Lightning Experience<\/figcaption><\/figure>\n
In above code, if we click first two URL, we will get an error. However, third URL will work.<\/p>\n
Key take away in this post is that, we need to use\u00a0sforce.one\u00a0<\/strong>object, which will be available by default in Lightning experience.<\/p>\n
Problem in above code and sforce.one API:<\/strong><\/p>\n
Above code will not be redirected properly on cancel button. so we can say even sforce.one is not full proof<\/strong>. In that scenario, we can use below snippet. Notice how URL is used here<\/p>\n
\r\nvar simpleURL = '\/one\/one.app#\/sObject\/Account\/new?nooverride=1&retURL=\/001' ; \r\n                sforce.one.navigateToURL(encodeURI(simpleURL));\r\n<\/pre>\n
Its too early to party \ud83d\ude41 . Above code will work only in Summer 17 but not in previous release.<\/p>\n
I was not able to find solution which will work in Summer 17<\/a> as well as in Spring 17<\/a>. Please drop a comment if you know the answer else we have to live with this code, as anyways all instances would be moved to Summer 17<\/a> in few weeks.<\/p>\n
Below Video shows the issue and its fix discussed in this post.<\/p>\n