[SalesForce] Use variable from lightning:recordEditForm in aura:if

I would like to know if it's possible to evaluate the expression from the RecordEditForm.

This component's "else" is never hit. Are aura if tags supported within RecordEditForms?

Comments__c is a Text field.

<aura:component implements="flexipage:availableForRecordHome,force:hasRecordId">
<aura:attribute name="anyAccount" type="String" access="public"/>

 <lightning:card class="slds-text-heading_small slds-card_boundary" title="{!'Account Type : ' + v.anyAccount }" >
     
    <lightning:recordEditForm recordId="{!v.recordId}"
                          aura:id="editRecord"
                          objectApiName="Account"
                         >
        <!-- onsubmit belongs to the button within the form -->
        <center><strong><lightning:outputField fieldName="Name" /></strong></center>
        <lightning:inputField fieldName="Industry" />
        <lightning:outputField fieldName="Industry" />
       
        <aura:if isTrue="{!empty(v.Comments__c)}">
            <lightning:inputField fieldName="Send_To_ERP__c" />
            <aura:set attribute="else">
                This Account is in ERP
            </aura:set>
        </aura:if>
     </lightning:recordEditForm>        
        <center><lightning:button class="slds-m-top_small" variant="brand" type="submit" name="update" label="Update Account" onclick="{!c.update}" /></center> 
     
 </lightning:card>

</aura:component>

You should see different outcomes

Best Answer

modify your code to below format. you missed value attribute and empty check

    <aura:component implements="flexipage:availableForRecordHome,force:hasRecordId">
<aura:attribute name="anyAccount" type="String" access="public"/>
<aura:attribute name="commentchk" type="Boolean" default="false"/>

 <lightning:card class="slds-text-heading_small slds-card_boundary" title="{!'Account Type : ' + v.anyAccount }" >

    <lightning:recordEditForm recordId="{!v.recordId}"
                          aura:id="editRecord"
                          objectApiName="Account"
                          onload="{!c.handleOnload}"
                         >
        <!-- onsubmit belongs to the button within the form -->
        <center><strong><lightning:outputField fieldName="Name" /></strong></center>
        <lightning:inputField fieldName="Industry" />
        <lightning:outputField fieldName="Industry" />

        <aura:if isTrue="{!v.commentchk)}">
            <lightning:inputField fieldName="Send_To_ERP__c" />
            <aura:set attribute="else">
                This Account is in ERP
            </aura:set>
        </aura:if>
     </lightning:recordEditForm>        
        <center><lightning:button class="slds-m-top_small" variant="brand" 
           type="submit" name="update" label="Update Account" onclick=" 
            {!c.update}" /></center> 

        </lightning:card>

       </aura:component>

controller.js

 ({
   handleOnload : function(component,event,helper){
   var recUi = event.getParam("recordUi");
    if($A.util.isEmpty(recUi.record.fields["Comments__c"].value)){
     component.set("v.commentchk", true);
    }

   },
})

Related Solutions

[SalesForce] Is it possible to use lightning:recordEditForm dynamically on different object types with variable objectApiName

So I faced a similar issue, I managed to solve it using aura:if

aura:if doesnt create the inner components unless the condition is true. You can use it to your advantage.

<aura:if isTrue="{!!empty(v.ParentType)}">
<lightning:recordEditForm recordId="{!v.recordId}"  objectApiName="{!v.ParentType}">
</aura:if>

The inner component and its contents are only created and rendered if the value of the isTrue expression evaluates to true. If the value of the isTrue expression changes and evaluates to false, all the components inside the tag are destroyed. The components are created again if the isTrue expression changes again and evaluates to true.

The general guideline is to use because it helps your components load faster initially by deferring the creation and rendering of the enclosed element tree until the condition is fulfilled.

Thus when your component is loaded even before calling init event, lightning:recordEditForm wont render as v.ParentType will be null.

After your init is called and you set the value of v.ParentType then automatically it will start rendering the lightning:recordEditForm. As ParentType is not null, it wont throw an ugly error.

SRC: https://developer.salesforce.com/docs/atlas.en-us.lightning.meta/lightning/components_conditional_markup.htm

[SalesForce] How to use $A.createComponents() on lightning:recordEditForm with nested lightning:inputField

I came up with a way to do this; you have to create the children first, and then the parent, similar to how the system would do it in mockup. Here's a demonstration:

<aura:application extends="force:slds">
    <aura:attribute name="recordEdit" type="Aura.Component[]" />
    <aura:handler name="init" value="{!this}" action="{!c.init}" />
    {!v.recordEdit}
</aura:application>

({
    init: function(component, event, helper) {
        // First, create children
        $A.createComponents([
            ["lightning:inputField", { fieldName: "Name"}],
            ["lightning:inputField", { fieldName: "Industry" }]
        ], (components, status, errors) => {
            // Then parent, specifying body of lightning:inputFields
            $A.createComponents(
            [["lightning:recordEditForm", { recordTypeId: "01250000000QNyF", objectApiName: "Account", body: components }]], 
                            (components, status, errors) => {
                                component.set("v.recordEdit", components);
                            });
        });
    }
})

Best Answer

Related Solutions

[SalesForce] Is it possible to use lightning:recordEditForm dynamically on different object types with variable objectApiName

[SalesForce] How to use $A.createComponents() on lightning:recordEditForm with nested lightning:inputField

Related Topic