18

We're running into this too. We expected it to be the case that if we navigate to a Lightning Component URL once, then walk through other pages, then navigate back to it with a different URL, we'll get a brand new instance and see the init method fire. Instead we get a stale older version with no init fired. So it's not clear what to do if what we really ...


9

Not an immediate answer, but the long term solution would be to indicate the known issue affects you Lightning Component force:showToast event displays toast message behind action window in Lightning Experience and Salesforce1


8

I've eventually found a solution. The following script has to be included: <script type='text/javascript' src='/canvas/sdk/js/publisher.js'></script> Then use this line to close the Quick Action window: Sfdc.canvas.publisher.publish({ name: "publisher.close", payload:{ refresh: "true" }});


5

I found a relevant approach. In the component with lightning:isUrlAddressable simply add a change handler for the pageReference state. Component: <aura:handler name="change" value="{!v.pageReference}" action="{!c.reInit}" /> Controller.js: reInit : function(component, event, helper) { $A.get('e.force:refreshView').fire(); }


5

Okay looks like documentation is a bit messed. This is what I found by trying all pester - Stays for 3 seconds, No close symbol sticky - Stays infinitely or Until you press the close button dismissable - Stays for 3 seconds, you can close it by pressing close button.


4

You can use the lightning:notificationsLibrary and put a notice up over your modal. It's not the same as a toast, but might work in some cases.


4

I have also been suffering form this issue. I use a lightning.recordEditForm component with some visible and some hidden lightning:inputField elements inside it, to create a clone Quote record inside a Quote record. My debug findings: This is the JSON that onerror event returns from server for this error: {"error":{"statusCode":400,"errorCode":"...


3

You can call a quick action but only if you are on the record page and that page has the quick action you are trying to call. https://developer.salesforce.com/docs/component-library/bundle/lightning:quickActionAPI/documentation I spent forever trying to use this to find it a fail... What you can do is use your javascript controller to go to the component ...


3

Due to the Locker-Service, you can not communicate with the container app. Either use the force:lightningQuickActionWithoutHeader interface or use the bundle version less than 39.0. You can verify it by executing the same code snippet in chrome console. If you get something in the Chrome console then Lightning Locker Service is creating an isolation layer. ...


3

I ran across a similar problem recently and opened a case with Salesforce. I was told that, right now, it isn't possible to use special characters in "Toasts", which is what the app is using to display the success message. Take a look: https://developer.salesforce.com/blogs/developer-relations/2017/08/displaying-user-notifications-lightning-component-...


3

As mentioned in the release notes :https://releasenotes.docs.salesforce.com/en-us/spring16/release-notes/rn_networks_templates_more_record_actions_napili.htm Community members with the necessary permissions can follow the record and use the quick actions defined for the object from the record banner on a record detail page. Previously, they could only edit ...


3

I'm afraid that's currently not possible (Summer '18). You can add quick actions to list view but not the ones that are invoking lightning components. I tried for example to create quick action that creates a record then I added it to a list view from Setup-> Object Manager -> Desired Object -> Search layouts -> List View -> Click edit -> Move quick ...


3

You can also use the aura:html tag to achieve this. Works for API version > 42: <aura:html tag="style"> .cuf-scroller-outside { background-color: white; } </aura:html>


3

NOTE This is a hack and completely experimental, it may break between releases due to CSS class changes and works as of Spring 18. The background color is coming from a app.css class .cuf-scroller-outside. If you override this class you can change the background color. Basically, you have to add this following CSS inside the HTML markup. <style> ....


3

The force:LightningQuickAction interface only allows the component to be used as a quick action - it doesn't automatically handle loading it in a modal. It will load in a modal if it's used as a quick action, but if it's used outside of that context then you'll need to handle creating the modal to load your component into.


2

As it turns out, I needed to select From Predefined Field Name instead of From Address. After choosing that option, I was able to select one of the existing validated email address I have setup in my org from a picklist: I tested this, and now the Email Case Action defaults to the FROM address I specified.


2

Your modal box is splitting into separate sections as you are not wrapping it correctly. For example, your modal is not wrapped in a section tag as documented at Modals. you have removed the modal__container class amongst other important secltions and classes from the documented one, so your component is most likely suffering from SLDS scoping issues from ...


2

You Can create an attribute in your Main component as <aura:attribute name="source" type="String" default="detail" /> There is no way you can set an attribute from Quick Action while calling component directly. You can use an intermediate component though. While calling the Main component from Intermediate component, you can set the Source value as "...


2

Lightning Quick Action/Lightning Component Actions is only available in Salesforce mobile app and Lightning Experience. The document you have share have the only describe Quick Action Not about Lightning Quick Action/Lightning Component Actions. Use the following link for more details:- https://help.salesforce.com/articleView?id=lightning_component_actions....


2

You should check your custom object layout; If the red highlighted area as above screenshot, then click there, it will be as below )or it's already as below. Then you can drag&drop the buttons away from the area.


2

Hope, you've created a quick action button with Lightning Component. Lightning component will be fired only on button click. You cannot disable a quick action. Instead you can throw some message from your doInit function if the conditions are not met. Hope this helps.


2

I have the same issue with you, aura init event is not getting fired when second time visits the same lightning component. My workaround is firing the refresh event after navigating to the Lightning component. navigateToMyCmp : function(component, event, helper) { event.preventDefault(); var pageReference = { type: 'standard__component', ...


2

release notes of 44.0 API saying that lightning list view actions are mentioned in massQuickActions tag in searchLayout section of object. Example from documentation <?xml version="1.0" encoding="UTF-8"?> <CustomObject xmlns="http://soap.sforce.com/2006/04/metadata"> . . . <searchLayouts> <listViewButtons>New</...


2

It's case sensitive, you have recordid and recordId. recordId is what you're using in your init method so that's probably the correct casing. Try create : function(component, event, helper) { alert(component.get("v.recordId")); }


2

For list buttons I would suggest using URL buttons in combination with lightning:isUrlAddressable interface. Using a component you are not moving outside of standard Lightning Application so there is no need to add any dependencies. So your url would look something like that: /lightning/cmp/c__CreateRecord?c__accId={!Opportunity.AccountId}&c__oppId={!...


2

I think it would be better understood by going to basics - by understanding difference between lightning and visualforce. Visualforce to apex is synchronous transaction, thus when pageReference object from apex is returned to a visualforce action, it will perform navigation. Lightning to apex is asynchronous transaction, thus all the data transfer takes ...


1

Why do you even need lightning component here. Looks to me like all you're doing here is just updating a field value on contact. You can Create Object-Specific Quick Actions and use update a record action instead of lightning component to update the checkbox field. UPDATE BASED ON COMMENTS: Instead of using init to get data from Lightning Data Service I ...


1

@redDevil's Comment on the question answered it: The helper.close dialogue should be within the call back if you want that to get executed after server response comes back.


1

You can set predefined value only for Creating Object-Specific Quick Actions in salesforce. It means you should select an action type as "create a record", While you are going for action having the source as Lightning Component you can not do it. If you are creating a record or editing it, You can modify your lightning component accordingly to set the ...


1

Thanks to the questionably titled "possible duplicate", pointed out by @Jayant Das, I was able to piece together a solution. My component need to interrupt the submit process. I was able to do this with: <lightning:recordEditForm objectApiName="Opportunity" recordId="{!v.recordId}" onsubmit="{!c.sendRequest}" > Not strictly necessary, but for ...


Only top voted, non community-wiki answers of a minimum length are eligible