New answers tagged

1

Some of the attributes for lightning:input are different from ui:inputText ui:inputText attribute specification lightning:input attribute specification The following attributes from your markup for lightning:input is not supported: click, updateOn and keyup. This is why it is throwing an error. There are different attributes for handling these changes like: ...


1

The type attribute is the type of resource that the component depends on. The default value is COMPONENT. The most commonly used values are: COMPONENT EVENT INTERFACE APPLICATION Use a comma-separated list for multiple types; for example: COMPONENT, APPLICATION. The type, date you need to pass into the attributes of the component which is opt in your ...


0

i figured it out. removed the html-5 doctype and used actionregion and this resolved the issue. Looks like it was html5 that was causing an added layer of validation i even when actionregion was being used. Quick fix...don't use html5 for now.


0

This seems to work when attempted independnetly, using execute anonymous via the sfdx CLI for example: >> Start typing Apex code. Press the Enter key after each line, >> then press CTRL+D when finished. > String enteredText1 = 'a610V0000015C5DQAU'; Id myId = Id.valueOf(enteredText1); > System.debug(myId); Compiled successfully. Executed ...


0

You are in controller function which is in Javascript and Javascript is Case-Sensitive. You are using True, which is not present in javascript. Try updating this block - First way if(res[0].Integrated_lead__c && res[1].Integrated_lead__c ){ toastEvt('Selected Leads are integrated Leads and cannot be merged'); } Second way if(res[0]....


0

Not sure whether it is the behaviour but when i removed disabled = true from the field, i was able to access the values.


0

To get the difference in times, you can use some parsing: update: function(component, event, helper) { let start = component.find("start").get("v.value"); let end = component.find("end").get("v.value"); if(start && end) { let startSec = start.split(/:/).reduce((p,v)=>p*60+parseFloat(v),0);...


0

You may want to look at some of the code of these invocable actions. They show common patterns: https://unofficialsf.com/flow-actions/ (generally there's a link to source code at the bottom of each piece of documentation) basically, set up a new apex class called something like MergeCase. Give it a method like 'execute' and put the invocable method on that. ...


Top 50 recent answers are included