[SalesForce] Picklist Values in Dynamic Lightning Components

Is there an out-of-the-box solution to populate record-type specific picklist values when creating a picklist dynamically (in a Lightning Component) that references an sObject field?

At this point it looks like all picklist (ui:inputSelect) values must be created as ui:inputSelectOptions and will not populate dynamically. This is problematic for record types since we can't get record-type specific picklist values from the server-side controller.

Also, thoughts/best practices for handling dependent picklists?

Your insights are appreciated.

Best Answer

After switching from ui:inputSelect to lightning:select , I was able to use the standard html options.

MyComponent.cmp

<aura:attribute name="options" type="String[]" />
<aura:handler name="init" value="{!this}" action="{!c.doinit}" />
<aura:attribute name="selectValue" type="String" />
<lightning:select aura:id="myselection" value="{!v.selectValue}">
<aura:iteration items="{!v.options}" item="option">
<option value="{!option}">{!option}</option>
</aura:iteration>
</lightning:select>

MyComponent.controller

doInit:function(component,event,helper){
component.set('v.options',['jan','feb','mar']);
component.find('myselection').set('v.value','feb');
}

Related Solutions

[SalesForce] When is it appropriate to use Record Types

Record types are primarily used when you want to identify or "group" records that are used for a similar purpose or where its beneficial to identify them as being "related" or "similar".

Your question covers more than just record types. It also addresses how they can be utilized in terms of file sharing, restricting basic CRUD and impacting profiles. Your question interrelates all these issues.

Solution 1 assumes the need for two record types when perhaps there's only a need for one? Why do I say that? It appears to me that you primarily want to identify the records that either "belong" to or were "created by" Team A. Is that the case? After all, Team B can edit anything created or owned by Team A. So does Team B need their own record type? That's not totally clear yet.

As we know, there are often many ways of doing things in SF. I think there's an option that might suit your needs which you've not yet considered and that's Publisher Actions. You could have a Publisher Action that creates a new account based on the requirements needed for Team A and another Publisher Action based on the requirements needed for Team B. Both could use the same page layout, but only Team B Profile Users could also edit not only records created with the Team A Publisher Action, but also those created with the Team B Publisher Action. For those users with a Team A Profile, all fields they can't edit, would be read only unless you wanted them to have their own page layout appropriate for their profile.

Unless I'm mistaken, you could utilize record types for the above if you want to, or have new records default to the appropriate Publisher Action for the User Profile accessing the page. Whether to use record types really depends on whether or not there's a valid reason to segregate or "denote" a difference between records created by the two different teams and who has edit access to them.

I hope this answer is helpful to you. For more on this, I highly recommend you refer to Force.com Platform Fundamentals.

[SalesForce] How to populate picklist values in Lightning Componets according to the metadata definition

There is something...

I found this post Lightning - How to use force:inputField? and I'm validating this markup

<force:inputField value="{!v.YourAttributeNameForTheSObject.YourFieldname}" />

It's in the documentation

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

The description is very puristic (no further explanation, no example) and this is currently the only match in the documentation I found. It leaves many questions open.

And it works partly. As @Andrew discoverd, picklists come up disabled. Using jQuery to wipe the disabled="" makes them editable and I was surprisingly be able to change a picklist-value and get it saved.

So what does this tell us?

Is this officially available or not?
What is it capable of and what not?
Should we use it or not?
Will there be an improvement of documentation and functionality soon?

Please let us know, so that we can plan ahead. This is nothing small. This is very very big - at least in my opinion, since to use ui:inputXXXX is very poor compared to force:inputField

Best Answer

Related Solutions

[SalesForce] When is it appropriate to use Record Types

[SalesForce] How to populate picklist values in Lightning Componets according to the metadata definition

Related Topic