Expressions enable us to dynamically control the rendering and display of elements in the markup based on specified conditions. Aura Expressions In Aura, as shown above, we can directly write expressions in the markup. However, in LWC, it is not possible to directly write expressions in the markup. Instead, we need to write expressions in …
Utilizing Expressions in LWC with if true and if:false Read More »
INTRODUCTION Occasionally, there may be a need to include or alter field values during the onsubmit event of lightning:recordeditform. In the following example, I am creating a record for the ‘Lead’ object using lightning:recordeditform, and within the onsubmit event, I am appending the ‘Description’ field value for the ‘Lead’ object. Aura Component: JavaScript controller:
Starting from Salesforce Spring ’18, the lightning:overlayLibrary tag was introduced to display messages using modals and popovers. This component requires API version 41.0 or later and is not supported in lightning applications. It is only supported in Salesforce Lightning Experience, Console, and Communities. In the following example, the components used are: Component – Sample JavaScript …
Modal created using the Lightning OverlayLibrary Read More »
The helpText in lightning out is not being displayed correctly due to a problem with Salesforce Lightning CSS. To ensure proper display of the helptext, you can utilize the provided styles in your Visualforce page. Style Sheets:
The lightning:formattedUrl component renders a hyperlink with an href attribute, presenting a read-only representation of a URL. The URL can be either relative or absolute. Code Example: <aura:component> <aura:attribute name=”recordId” type=”String” default=”0063X0000146rTLQAY”/> <lightning:formattedUrl value=”{!’/’ + recordId}” tooltip=”Opportunity” label=”Opportunity” target=”_blank” /> </aura:component>
Apex Class: Lightning Component: Lightning JS Controller: Lightning JS Helper:
Always choose Lightning Web Components unless you need a feature that isn’t supported. There are following features which are not supported in LWC.
