LWC Quick Action for Task

lightning-aura-componentslightning-web-componentsquickaction

I'm working on a Quick Action for the first time (ScreenAction in this case) for a Task object. I've created an LWC component, embedded in the Aura component to make it available for Task.

<aura:component implements="force:lightningQuickActionWithoutHeader, force:hasRecordId">
    <c:LWC recordId="{!v.recordId}">
</aura:component>

The problem is that in LWC I cannot get the recordId of the Task. I've tried using @api recordId, connectedCallback and renderedCallback but nothing worked for me, everytime the result was undefined. Why is it like that? Is Task object the reason or is it something else?

Best Answer

LWC Quick Actions are not supported for Task object.

You'll get an error when creating a QA for LWC on Task record:

Lightning Web Component quick actions are not supported for this entity

I managed to get the recordId from a Task record in an Aura Component:

<aura:component implements="force:lightningQuickAction,force:hasRecordId">
    <aura:attribute name="recordId" type="String" />
    
    <div>
    {!v.recordId}
    </div>
</aura:component>

Summary: It could be that your Aura Component does not receive recordId because of some typo in your code, or if it does receive, the whole component crashes because of the LWC embedded inside your Aura Component. Please check both of these possible scenarios.

Related Solutions

[SalesForce] window.onload equivalent for aura components

In my experience with aura, anything involving Lightning Data Service has to be considered to be an async operation, so you need to be looking for the recordUpdated event rather than trying to use recordId in init - per the docs:

"force:recordData loads data asynchronously by design since it may go to the server to retrieve data. To track when the record is loaded or changed, use the recordUpdated event as shown in the previous example. Alternatively, you can place a change handler on the attribute provided to targetRecord or targetFields."

So without seeing more of the markup, I am not sure where the handler would go, but you would need to have an event similar to they are handling Loading a Record in the docs.

[SalesForce] LWC renderedCallback not retrieving a wired record

From the documentation:

When a component rerenders, all the expressions used in the template are reevaluated. Due to mutations, a component is usually rendered many times during its lifespan in an application.

Now, as you are not using platoonEvent in the markup, the expression won't be evaluated, and the wire won't be called.

Fix: Use platoonEvent in the markup like

  <template>

    In my template

     Record Id is : {recordId}
    <br/>
    <template if:true={platoonEvent.data}>
        {platoonEvent.data.fields.Service_Platoon__c.value}
    </template>
</template>

Also the thing to remember is renderedCallback will be called multiple times, the first time its called, it won't have the value. You can see it from your debug logs

Best Answer

Related Solutions

[SalesForce] window.onload equivalent for aura components

[SalesForce] LWC renderedCallback not retrieving a wired record

Related Topic