6

I found a workaround if you want to continue using the lwc quick action(as I do :)). You can use NavigationMixin and have it Navigate to the record page you're on. this[NavigationMixin.Navigate]({ type: "standard__recordPage", attributes: { recordId: this.recordId, ...


5

As the error states: Lightning Web Components quick actions are not supported for this entity (emphasis mine) That means that you can use LWCs as Quick Actions, but not on Work Orders. The documentation also says: NOTE LWC quick actions are currently supported only on record pages. LWCs only recently gained any Quick Action support, and it will likely ...


3

Per today's Summer 21 release webinar, you will need to do two things Add a new import: import { CloseActionScreenEvent } from 'lightning/actions'; Then add a simple method to close it: closeQuickAction() { this.dispatchEvent(new CloseActionScreenEvent()); } You can then call that and it will close the quick action. More details here H/T to ...


2

It appears this is still not a standard function for salesforce, but I found this work around. You can drag and drop this lightning component to any lightning page your quick action is on and it will redirect to the newly created record. It uses the link from the default success toast message so be sure to leave the 'Success Message' field blank. Hope it ...


2

this url : /lightning/cmp/runtime_sales_lead__convertDesktopConsole?leadConvert__leadId=' + recordId will be this work if we are opening the same url in mobile browser or from salesforce1 App ? please let me now


2

You have the following problems: Do not wrap fields in double quotes You concatenate strings using the & operator You can add line breaks using the BR() function Corrected: Property__c.Site_Contact__c & BR() & Property__c.Property_Group__r.Name & BR() & etc...


2

Salesforce has recognised that as a known issue and currently there is no suggested workaround. Interface validation is failing incorrectly on package install when a lightning component that extends another lightning component which implements the required quick action interfaces (force:lightningQuickAction / force:lightningQuickActionWithoutHeader) Source:...


2

Object-specific quick actions need to have a relationship field between the source object (object you're adding the button to) and the target object you're creating. For example, on an Account you might want to quickly create an Opportunity that is related to the Account. This is possible with a quick action as the Opportunity has a relationship to Account ...


2

This is a platform limitation and articulated here. Quoting from the docs below NOTE Actions on user profiles, cases, and work orders can appear in a different way than on other records. Actions on the user profile page come from the Quick Actions in the Salesforce Classic Publisher section of the global publisher layout. Only standard Chatter actions ...


2

Working codebase using the CSS from SLDS. Try not to use custom divs and pixels based height/width will not work well in all screen types A side note - You should start using LWC components instead of aura. Soon aura will be outdated in the Salesforce ecosystem. and LWC gels with existing builds where aura is used extensively <aura:component implements=&...


1

Okay, I think I figured out what was going on. The lightning web components targeted at lightning_RecordAction are headless, so the recordId is not passed to connectedCallback(). However, it is passed to the invoke() method if the recordId has been declared appropriately.


1

Consider using Dynamic Actions. You'll need to have a (typically Checkbox) field that tracks that the given action has been performed against the current record. If you do this, you can use this field in the action's visibility expression.


1

I found the solution in this blog. You can hide the Aura Modal using the CSS in the blog and the rest is straight forward.


1

You can't, you still have to use a Visualforce page with standard list controller and pass the records to the aura component using lightning out, as explained in Custom List view buttons in the lightning environment - this feature request is on the roadmap, but I don't know when it will be delivered. Here you have a sample implementation of how to do it.


1

I would recommend to build the quick action using force:lightningQuickActionWithoutHeader. If you want to stick to the force:lightningQuickAction you can try to add the following code as pointed out in this idea: https://trailblazer.salesforce.com/ideaView?id=0873A0000003Sq6QAE: ({ afterRender: function (component, helper) { this.superAfterRender(); ...


1

Assuming this is a VF page/controller on a standard object associated to the quickaction, then you can get the record ID as follows: public class MyController { ApexPages.StandardController ctrl; Id orderId { get {return this.ctrl.getId();} set; } public Order myOrder { get {return [SELECT ... FROM Order WHERE id = :this.orderId];} ...


1

To make the quick action visible in Lightning, you'll also need to add it to "Salesforce Mobile and Lightning Experience Actions". Adding some screenshots to make it easier for you As you can see in the above image, I added this button under the Lightning actions. And then it's available under actions on the Account lightning page.


1

Aura Component linked to button: <aura:component implements="flexipage:availableForAllPageTypes, force:lightningQuickActionWithoutHeader,force:hasRecordId" access="global" > <aura:html tag="style"> .slds-modal { visibility: hidden; display: none; } .slds-backdrop { ...


1

You need to use QuickAction.describeQuickActions and then get default values. List<QuickAction.DescribeQuickActionResult> result = QuickAction.DescribeQuickActions(new List<String> { 'Case.SendEmail'}); System.debug(result[0].getDefaultValues());


1

self-answering as this took me a while to figure out so hopefully this helps the next person Because this was an existing Community and the Contact Support button had worked previously, consider what changed. In this example, recordtypes were added to Case where none had existed previously. So, what you need to do: Grant Guest user access to the ...


1

You cannot add custom action on the related list. However, you can use a custom button on the related list. Review below Idea link Add quick actions on related lists


1

You cannot remove the opening of the model, it will be there. I would suggest to show messages in the quick action model instead of a toast using slds alert. https://www.lightningdesignsystem.com/components/alert/ That way users can see multiple messages, they wouldn't need to close 2 things.


1

If you create a text variable in your flow called "recordId" the action will automatically populate it with the ID of the record you are on. Sounds weird, but it works.


1

Now you can add a quick action on highlight panel on case object lightning record page even if feed tracking is enabled by upgrading to dynamic action which is a new feature in winter 21. Now, its your choice weather you want to keep action on feed tab or on highlight panel. Reference: - ADD QUICK ACTION IN HIGHLIGHT PANEL ON CASE OBJECT LIGHTNING RECORD ...


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