3

It's not supported for Quick Actions as mentioned here. There's an idea to support this that I suggest voting on. Unsupported Experiences and Tools Lightning Web Components doesn’t currently support these Salesforce experiences and tools. To use a Lightning web component with these experiences and tools, wrap the component in an Aura component. ...


2

A small grammar error: @wire(getRecord, { recordId: "$recordId", oppFields }) Defines a property oppFields on the parameters, but it needs to be fields: @wire(getRecord, { recordId: "$recordId", fields: oppFields })


2

I was facing the same issue and I confirm it it works in lightning. However, I found out following issues in my code: Mostly people just copy and paste code from here or any article: https://releasenotes.docs.salesforce.com/en-us/summer18/release-notes/rn_cases_email_apex_default_fields.htm global void onInitDefaults(QuickAction.QuickActionDefaults[] ...


2

This looks like a list view for a given object. You can edit the buttons that display by editing your list view Search Layout for the given object. Setup --> your desired object --> Search Layouts for Salesforce Classic Click on the down arrow for "List View" layout and select "Edit". From here, you can uncheck standard buttons. For your situation, you're ...


1

This kind of inconsistencies is a known issue (under review): https://success.salesforce.com/issues_view?id=a1p3A000001Yn5PQAS. Mind that there are other inconsistencies under reviews as well in the current release (Spring '20). E.g. when fields used in Related Record components are updated multiple times, the RR component in some cases does not reflect the ...


1

You also have to set mode="EDIT" for that like this <force:recordData recordId="{!v.recordId}" fields="['CaseNumber','Status']" targetFields="{!v.record}" aura:id="recordData" mode="EDIT" recordUpdated="{!c.recordLoaded}" />


1

Silly thing! I didn't had a user in test class where Use_Default_Signature is set. This did the trick! Id loggedInUserId = UserInfo.getUserId(); User adminUser = [SELECT Id FROM User WHERE Id = :loggedInUserId]; adminUser.Use_Default_Signature__c = true; update adminUser;


1

As per the documentation: This component is not supported in Lightning Out, Lightning communities, or the Salesforce mobile app. (my emphasis)


1

You can try standard Js way window.location.reload()


1

Salesforce posted this article addressing this problem (which just kept me up for 3 hours): Deployment error 'no QuickAction named NewTask found' It has some suggestions, but none of them worked for me. Eventually, I just ripped all Platform & Quick actions out of the package then added them back in post-deploy. May not work for ISV who can't access the ...


1

As per now its not possible to invoke quick action from LWC, but possible with the combination of LWC and AURA Here is the link: http://theblogreaders.com/call-lightning-web-comopnent-salesforce-quickactions/


1

Make sure to turn on Email Delivery from No Access or System Email Only to All Email in Email > Deliverability. This will show the "Relationship Field" option that is hidden for some reason in the above error.


1

Salesforce Support has logged a bug internally. For reference, the work item is W-6965020. At the time of posting, I don't believe a "known issue" document has been issued.


1

All your code looks fine but fieldname in below line should be fieldName and it will work fine. Wrong:- <lightning:inputfield aura:id="opportunityProductField" fieldname="OpportunityId" value="{!v.recordId}" disabled="false" required="true"/> correct:- <lightning:inputfield aura:id="opportunityProductField" fieldName="OpportunityId" value="{!v....


1

This appears to be a part of the following known issue; https://success.salesforce.com/issues_view?id=a1p3A000001PYcdQAG


1

So answering my own question. Below is the response I received from Tier 3: lightning:navigation is supported in Communities however the page reference type for standard__component is not supported. So currently you can't navigate to a lightning component in Communities using lightning:navigation . Unfortunately force:navigateToComponent isn't supported ...


1

In this code , the fields defined in the force:recordData is not the correct way. Check the code below: Component:-> <aura:component implements="force:appHostable,flexipage:availableForAllPageTypes,flexipage:availableForRecordHome,force:hasRecordId,forceCommunity:availableForAllPageTypes,force:lightningQuickAction" access="global" > <aura:...


1

From what I understand clicking the new button on the related list customObject1 on the Account record - gives you the 'CustomObject1' value in the sObjectType attribute - whereas you want to have 'Account'. For this: You can use "Is Url Addressable" Component to get parent record (Account) details information like Id as you are on detail page of account. ...


1

Do you have translations? Sometimes if things get out of sync the translations can throw these errors. If you can, delete out the translations for the object, or at least make sure that they’re all in there. Specifically, page layouts all get translated, and if the page layout translation is wrong, the whole thing fails to deploy.


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