7

The following snippet works well on a sandbox that's still on Spring 16 Lightning Experience but gives the same code gives an error on a sandbox running the Summer 16 release from a visualforce page : <a href="{!URLFOR($Action.Candidate__c.New, null,null)}" class="slds-button slds-button--neutral" >New</a> . The following error comes up on the sandbox running the Summer 16 update :

Looks like there's a problem. We couldn't find the record you're trying to access. It may have been deleted by another user, or there may have been a system error. Ask your administrator for help. Does anyone know what could be the cause of this or if there is workaround ?

  • 2
    It seems like Salesforce is trying to take you to the detail page of a record, rather than the new/edit page. If you changed your code to <a href="{!URLFOR($Action.Candidate__c.New, null)}" class="slds-button slds-button--neutral" >New</a> does it work? – dBeltowski May 18 '16 at 20:47
  • @DougB changing the code to that still does not work – Dunisani Matt May 18 '16 at 21:06
  • Well the only thing I can suggest is you open a case with Salesforce. – dBeltowski May 19 '16 at 14:42
0

I've just tested this on our Summer '16 sandbox, and it seems to work fine.

<a href="{!URLFOR($Action.Custom_Object__c.New)}">Test</a>

The nulls can safely be left out on a link like this; give it a try if you haven't already. Hopefully it was just a bug that has been patched since.

| improve this answer | |

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.