The Stack Overflow podcast is back! Listen to an interview with our new CEO.
3

I think you may have to wrap your LWC in a traditional Aura component and then use isUrlAddressable interface https://developer.salesforce.com/docs/component-library/documentation/lwc/reference_page_reference_type


2

Hopefully you figured out this problem Calvin, I've been trying to work it out myself and found this, which helped solve it for me... https://developer.salesforce.com/forums/?id=9062I000000g555QAA Start with this promise, then call getEnclosingUtilityId, and inside that promise register the onUtilityClick event handler... doInit : function(component){ ...


2

You can just use a Map to do this, perhaps like this: Map<Id, ContentDocument[]> docsByAuthor = new Map<Id, ContentDocument[]>(); for(ContentDocument doc: [SELECT CreatedById FROM ContentDocument]) { ContentDocument[] docs = docsByAuthor.get(doc.CreatedById); if(docs == null) { docsByAuthor.put(doc.CreatedById, docs = new ContentDocument[...


1

it's not possible in standard Component , you can achieve your use case if you build custom lightning component with workspaceAPI


1

you should use lightning:overlayLibrary to show component as modal popup. first add overlay component in to your component then update your fire like below code snippet for your use case. cmp <lightning:overlayLibrary aura:id="overlayLib"/> cmpcontroller fire: function(component, event, helper) { var type = component.get("v.value"); ...


1

Don't define a default attribute. This causes the attribute to default to null. Eg <aura:attribute name="selectedObj" type="Object" />


1

your inserting just normal JS object in to Daily_Task__c[] type in your AddNewRow function, it's wrong you should insert Daily_Task__c sobject type what you did in success of doinit function. and addNewRow is Reusable function so as a best pratice you should declare Daily_Task__c sobject Aura attribute like below sample code. cmp <aura:attribute name="...


1

Poonar's comment above helped me figure out the solution but I though it might be easier to post it as an answer so that other folks can see the answer easier. The issue is that the Wrapper Class variables are not marked as @auraenabled - in the example above these would be changed to: public class payWrap{ @AuraEnabled public String name{get;set;} ...


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:...


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