Custom Metadata Types vs Custom Settings vs Custom Labels 💬 In plain words: Three lookalikes: Custom Metadata = configuration that DEPLOYS with your code (best for app settings). Custom Settings = org/user-specific values, changeable at runtime (hierarchy type is great for bypass switches). Custom Labels = translatable text for the UI. 📌 Example: API endpoint URLs per environment → Custom Metadata (deploys with code, sandbox vs prod values). A 'Bypass_Automation__c' checkbox an admin flips during data load → hierarchy Custom Setting. The word 'Submit' translated to Hindi → Custom Label. 🎬 Real-Life Example: The Fee Table Trapped Inside Code Skyline charges a different delivery fee per city. Apex needs those rates on every booking. The Old/Bad Way: if (city == 'Delhi') fee = 50. Else if (city == 'Mumbai') fee = 65. … Every rate change is a code change, a test run, and a deployment. Why this is bad: Business data is trappe...
Introduction:
In this blog post, we will explore how to create a sticky header in Lightning Web Components (LWC) in Salesforce. A sticky header is a commonly used UI pattern that keeps the header fixed at the top of the page while allowing the content to scroll beneath it. We will build a dynamic solution that can be easily reused in different LWC components. So let's dive in and create our sticky header!
Prerequisites:
Before proceeding, make sure you have a basic understanding of Lightning Web Components and Salesforce development. You should have a Salesforce Developer Edition org or a suitable Salesforce environment to try out the code examples provided.
Step 1: Setting up the LWC Component
Start by creating a new LWC component using the Salesforce CLI or the Developer Console. Let's name our component "StickyHeader".
Step 2: Writing the HTML Markup
In the StickyHeader.html file, we will define the structure for our sticky header. It will consist of an outer div that wraps the entire header and content, and an inner div for the header itself. Here's an example markup:
<template>
<div class="sticky-header">
<div class="header">
<!-- Add your header content here -->
</div>
<div class="content">
<!-- Add your main content here -->
</div>
</div>
</template>
Step 3: Implementing the Sticky Header CSS
Next, we need to add CSS styles to make our header sticky. Open the StickyHeader.css file and add the following styles:
.sticky-header {
position: relative;
}
.header {
position: sticky;
top: 0;
z-index: 1;
/* Add your desired styles for the header */
}
.content {
/* Add your desired styles for the content */
}
Step 4: Handling Dynamic Content
To make our sticky header component dynamic, we need to add properties to accept custom content from the parent component. Open the StickyHeader.js file and modify it as follows:
import { LightningElement, api } from 'lwc';
export default class StickyHeader extends LightningElement {
@api headerContent;
@api mainContent;
}
Step 5: Using the Sticky Header Component
Now we can use our sticky header component in other LWC components by passing custom content. Here's an example of how to use it:
<template>
<c-sticky-header header-content={headerContent} main-content={mainContent}></c-sticky-header>
</template>
Remember to define the headerContent and mainContent properties in the parent component's JavaScript file and assign appropriate values.
Conclusion:
Congratulations! You have successfully created a dynamic sticky header component in LWC for Salesforce. You can now reuse this component in different parts of your application to achieve a consistent user experience. Feel free to customize the styles and add additional functionality based on your requirements.
Sticky headers are widely used in web applications to improve usability and navigation. By implementing this functionality in LWC, you can enhance the user experience of your Salesforce application. Enjoy building amazing Lightning Web Components with sticky headers!
That wraps up our blog post. We hope you found this tutorial helpful. If you have any questions or feedback, please leave a comment below. Happy coding!