Skip to main content

Dynamic Field Binding in Salesforce


This tip is useful when we are going to display different field for different users.We can avoid non empty field from displaying in visualforce page by using rendered property.   We can write  rendered="{!IF(NOT(ISNULL(Field)),true,false)}". If field has some value then condition becomes true , that means rendered is true . So field is displayed .  Its a simple one , then  what is the use of this tip ...?
 Suppose we have 20 fields in an object and an user wants to display those fields which has some value . So we will do easily using rendered property . But we have to write rendered property in every field . is not this a clumsy one...?  We always write short code satisfying our requirement . what If we use that rendered property only once to solve our requirement. is not it easy...? Here is my page code...
 
<apex:page controller="Renderfieldcontroller">
  <apex:form >
    <apex:pageBlock >
       <apex:pageBlockSection columns="2" title="Book Information" rendered="{!Enable!='show'}">
      
          <apex:repeat value="{!threeFieldList}" var="afield" >

              <apex:inputField value="{!Book[afield]}"  />
          </apex:repeat><br/>
         
          <apex:commandButton value="Save" action="{!savingBook}"/>
      
       </apex:pageBlockSection>
      
       <apex:pageBlockSection columns="2" title="Book Information" rendered="{!Enable=='show'}">
     
          <apex:repeat value="{!threeFieldList}" var="afield" >

              <apex:outputField value="{!Book[afield]}" rendered="{!IF(NOT(ISNULL(Book[afield])),true,false)}"  />
          </apex:repeat><br/>
       </apex:pageBlockSection>
      
    </apex:pageBlock>
    </apex:form>
    </apex:page>
 
Now My controller......
 
public class Renderfieldcontroller {

   List<string>threeFieldList{get; set;}
   public final Book__c bok{get;set;}
   public String Enable{get;set;}

   public Renderfieldcontroller () {
      bok = new Book__c ();
      if (threeFieldList == null) {

             threeFieldList = new List<String>();
             threeFieldList.add('Author__c');
             threeFieldList.add('Price__c');
             threeFieldList.add('Publisher__c');
             threeFieldList.add('Title__c');
               
        }

      }
     
    public List<String> getthreeFieldList() {
        return threeFieldList;
     }
        
    public Book__c getBook() {
       return bok;
     }
         
    public PageReference savingBook() {
         upsert bok;
         Enable = 'show';
         return null;
     }
  }
 
Labels:

Comments

Post a Comment

Popular posts from this blog

How to Create a Tooltip in Lightning Datatable ?

Imagine you have a datatable displaying a list of Contact records , and one of the columns shows the Account Name . The Account Name is a hyperlink that allows users to navigate to the Account record page. But what if users want to take a quick glance at some key Account fields —like Phone or Address—without navigating to the Account record? In Salesforce Classic, this was achieved using the Mini Page Layout feature from standard page. However, in Lightning Experience, we can implement a similar feature by adding a tooltip to the data table. Solution Overview: We’ll create a Lightning Web Component (LWC) that: Displays a data table with a clickable Account Name . Provides a tooltip that shows the Account's Phone and Address fields when users hover over the Account Name. Implementation Steps: 1. Data Preparation We need to retrieve the following fields for each Contact and its associated Account: Contact Fields : Name, Phone, Email Account Fields : Name, Phone, Billing Addre...
Post a Comment
Read more

Lifecycle hooks in LWC

There are 3 phase of LWC component  1. Mounting  A. constructor, B. connnectedCallback C. render D. renderedCallback 2. UnMounting  A. disconnectedcallback 3. Error  A.errorcallback Note - render is not lifecycle hook, it is protected method of Lightning element class. Mounting Phase LWC Creation and Render Life cycle Constructor Method ·        This method called when component is instantiated and It flows from parent to child component. ·        Need to call Super() inside constructor method ·        Can’t access any component properties or child component because it’s not ready yet. ·        Host element can be accessed through “this. template” inside constructor method. ·        Don’t add any attributes to host inside constructor C   constructor (){          super (); //...
Post a Comment
Read more

Style in LWC

 Following are the ways we can apply in CSS in LWC. 1. Inline CCS Inline CSS is not recommended approaches, it is take highest priority among all CSS. style="color:green;font-size:10px;" is inline CSS added to div < template >     < lightning-card title = "Inline CSS" >         < div >             < div style = "color:green;font-size:10px;" > This is inline Style div </ div >         </ div >     </ lightning-card > </ template >  2. External CSS style can be applied to an elements such as h1, p,div span etc. It can applied to class using "." notation. for example .user{} It can also be applied to pseudo class.  for example .user:hover{} Id locator is not being used in LWC to apply style To apply external css, need to create separate CSS file, file name should be exactly matched with component name. for example - If component name is ...
Post a Comment
Read more