My Lightning Component app uses navigateToURL to allow lightning users (in a browser) to edit data in custom objects:

navigateToEdit : function(cmp, event, helper) {
    var articleId = cmp.get("v.articleId");
    var urlMain = '/one/one.app#/n/salesCenter_Edit_Article?id=';
    var urlEvent = $A.get("e.force:navigateToURL");
         "url": urlMain + articleId

While processing this, Salesforce inconsistently inserts "?source=aloha" into the URL, and as a result, the page won't load the record. If I manually take the "?source=aloha" out, the page loads the record as expected.


1 Answer 1


As @Keith C mentioned, related to the link he posted, you would have to create Publisher Actions/Quick Actions to replicate the functionality in lightning since:

As stated in the release notes of Spring 16

If you use URL custom buttons to pass parameters to standard pages in Salesforce Classic—such as pre-populating fields when creating a record—this behavior doesn’t work in Salesforce1 or Lightning Experience.

you might want to do object specific actions rather than try and do url hacks which are not supported.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .