[SalesForce] Lightning Component Attribute Configurable from Lightning Builder

I want all my components attribute to be available for configuration in Ligthtning builder, so an admin like person can override default values. How can I do that?

<aura:component controller="namespace.SObjectSearch" implements="flexipage:availableForAllPageTypes">
    <aura:attribute name="sobject" type="String" default="account"/>
    <aura:attribute name="query" type="String" default="Select Id, Name From Account"/>
    <aura:attribute name="fields" type="String[]" default="['Id', 'Name']"/>
    <form>
        <ui:inputText class="form-control" label="Search" aura:id="searchField" value="" placeholder="enter search string"/>
        <ui:button label="Submit" press="{!c.searchSObjects}"/>
    </form>
    <ul class="list-group">
        <aura:iteration var="sobj" items="{!v.sobjects}">
            <li class="list-group-item"><a aura:id="sobjid" target="_blank" href="{!'/' + sobj.Id}">{!sobj.Name}</a></li>   
            <!--<aura:iteration var="prop" items="{!v.properties}">
            </aura:iteration> -->
        </aura:iteration>
    </ul>
</aura:component>

Best Answer

You can do this by creating a design file for your component .

Now create a design file for your attributes

<design:component label="SobjectSearch">
<design:attribute name="sobject" label="sobject" description="Enter Sobject Name hereprincipal" />
<design:attribute name="query" label="query" description="Type query here" />
<design:attribute name="fields" label="fields" description="Enter comma separated fields" />

Only Boolean, Integer or String attributes can be exposed in design files.

Array of string will render as multi pick-list value .

The link from documentation

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

Related Solutions

[SalesForce] How to navigate from one lightning component to another lightning component

Seems there is an event missing from the documentation, I went through this last week. Try this..

Component markup

<ui:button label="ATTENDANCE" press="{!c.navigateToRollCall}"/>

Controller (I am using default namespace here for my component AttendanceRollCall)

navigateToRollCall : function(component, event, helper) {
    var evt = $A.get("e.force:navigateToComponent");
        evt.setParams({
            componentDef: "c:AttendanceRollCall",
            componentAttributes: {
                programId: component.get("v.program.Id")
            }
        });
    evt.fire();    
}

[SalesForce] Attribute Lightning Component

Without the full code sample it's tough to tell why Lookup__c field isn't present, but I'm betting it's because of object references.

This bit here

component.set("v.oldItem", component.get("v.item"));

Associates the v.oldItem object with a reference (in javascript not Lightning) to the v.item object.

Since you said you wanted v.oldItem not to change when v.item changed, I'm betting this is not what you wanted.

Try doing this as a cheap and dirty copy.

component.set("v.oldItem", JSON.parse(JSON.stringify(component.get("v.item"))));

See if that works.

We do not clone objects in Lightning, that would get messy perf wise, so primitives are done by value, objects (and arrays) are done by reference.

Best Answer

Related Solutions

[SalesForce] How to navigate from one lightning component to another lightning component

[SalesForce] Attribute Lightning Component

Related Topic