New answers tagged

-1

Apex class public class CreateContactcls { @AuraEnabled public static string createContact(Contact contObj){ system.debug('CONTACT@@'+contObj.FirstName); insert contObj; return contObj.Id; } } AURA COMPONENT <aura:component controller="CreateContactcls" implements="force:appHostable,flexipage:...


2

As you already mentioned, you must specify either a targetId or a targetPageRef. In your case, if you don't want to redirect the user to any page, simply set dummy id for targetId. This is also explicitly mentioned in the CustomNotification Class You must specify a target for a notification. The target can be specified using either the targetID or the ...


0

As Paul mentioned, you should build UI tests with a library such as Selenium and Webdriver.io. However, an important limitation of these type of tests is that they are tightly coupled with the DOM. If you or Salesforce introduces changes with a new release, you'll have to maintain your tests. I recommend that you take a look at the UTAM pilot. This pilot ...


1

You cannot customize the list view item's actions. Actions in Lightning Experience mention this: List view items support only specific standard actions, like Edit, Delete, or Change Owner. There's a couple lowly voted ideas asking for this ability: Custom actions on List view items Actions on List View Items for custom buttons You can customize the ...


0

I have another idea. Instead of controlling visibility for tab, why not duplicating the tabs component for every Record type and set the component visibility for each record type? In this case we could achieve the desired outcome which would look like conditional tab rendering, but in fact this will be conditional component rendering. Create two tabs ...


0

Just had a similar problem with the background page mis-behaving and changing to standard__recordPage for edit fixed it for me. I have both the edit case and the new case in my code and based on the documentation, separate types need to be used: let navigation; if (activityId) { // Supports clone, edit and view navigation = { ...


0

Update as of 2-Nov-2021 Now we simply have the button available for cases. Starting in Spring'21 release (around 27-Feb-2021), the Manual Sharing became available in Lightning Experience: Share Records with Manual Sharing not requiring custom solutions for accounts, opportunities, cases, contacts, leads, and custom objects.


Top 50 recent answers are included