[SalesForce] Required attribute and init handler in lightning component

I have the following in my component:

<aura:handler name="init" value="{!this}" action="{!c.doInit}"/>
<aura:attribute name="item" type="Camping_Item__c" required="true" />

Component's controller simply calls apex auraEnabled method (which is fetches one record of Camping_Item__c type) and sets v.item attribute.

When I try to run an app with this component, I get an error:

[NoErrorObjectAvailable] Aura.loadComponent(): Failed to initialize
application.

If I remove required="true" from aura:attribute all goes fine.

Why is that? Is it possible to use the required="true" property with init handler?

Best Answer

I am pretty sure that if you set required="true" then the app or component that declares your component needs to provide the item. For example if your component is called "Camponent" in namespace "c" then the parent app/component would need to have:

<c:Camponent item="{!v.someCampingItemThatAlreadyExists}" />

Now, if the parent's init method fills in that value, then you're fine because it won't even attempt to create the c:Camponent until the init method has finished.

Related Solutions

[SalesForce] unable to pass an Opportunity from a Lightning Component into an @AuraEnabled Apex controller method

I have found that not having default attributes can cause problems with binding.

UPDATE - this applies to ALL attributes, including the sobjectType and CloseDate .

Add all attributes (even if empty at this stage) that you want to write to the server, because if they are not at least initialised in the defaults area, they don't get sent.

Also there are perhaps some missing fields that are needed for the Opportunity to deserialize properly (in the internal deserialization routine that is called prior to passing it to your @AuraEnabled method).

So perhaps you could define your oppty attribute like this:

<aura:attribute name="opportunity" 
                type="Opportunity" 
                default="{ 'sobjectType': 'Opportunity',
                           'Name': 'New Opportunity',
                           'StageName': 'Initial Contact',
                           'CloseDate':'2016-08-01'} />

Or at least set the name and stage prior to passing it to your method.

Of course, you may be doing this already - I can't see what your console output is.

This is just a long shot, because you seem to have done everything else right.

[SalesForce] How to declare aura:handler properly? (Application Event vs. Component Event)

In general component event requires name attribute to be defined in the aura:handler. See the handling of component event for more info.

Look at the doc on force:recordSaveSuccess it pretty much clear that it is an component event, which is why it's handler without name defined threw an error.

Best Answer

Related Solutions

[SalesForce] unable to pass an Opportunity from a Lightning Component into an @AuraEnabled Apex controller method

[SalesForce] How to declare aura:handler properly? (Application Event vs. Component Event)

Related Topic