2
SecureEvent#setParam expects two parameters, a string and an object:
componentEvent.setParam('searchText', beerSearchInput);
If you want to use object notation, use the plural version, SecureEvent#setParams:
componentEvent.setParams({searchText: beerSearchInput});
2
This question has probably been asked many times in different forums. The hidden label in the lightning:select is creating the additional space
Include class="slds-m-top_medium" in the lightning:layoutItem for the buttons. Also, include the verticalAlign="center" in the lightning:layout.
Code should be as follows:
<aura:component ...
2
If you want to use certain special characters in an attribute value you must XML (or HTML) encode the character. To use "<" in this case you would simply use "<" instead. NB: the documentation referenced by the other answer suggests you could even use "le" as the operator instead.
However, it would be more effective to ...
2
You'll want to use the lightning:treeGrid. The children for each item are in a special attribute named _children. See the documentation (above) for all the details.
1
The type attribute is the type of resource that the component depends on. The default value is COMPONENT.
The most commonly used values are:
COMPONENT
EVENT
INTERFACE
APPLICATION
Use a comma-separated list for multiple types; for example: COMPONENT,
APPLICATION.
The type, date you need to pass into the attributes of the component which is opt in your ...
1
For comparing in component side, you can use Expression functions for better readability.
lessthanorequal
lessthanorequal(1,2)
Returns true if the first
argument is numerically less than or equal to the second argument. <=
or le
Ref - https://developer.salesforce.com/docs/atlas.en-us.lightning.meta/lightning/expr_functions.htm
1
There's no direct CSS support for this, and browsers are technically free to implement this feature any way they want to, so most scrollbars are bottom and right for x- and y-overflow. That said, I found a nice trick that may serve your purposes:
<style>
div.top-scrollbars {
transform: rotateX(180deg);
}
div.top-scrollbars * {
transform: ...
1
Some of the attributes for lightning:input are different from ui:inputText
ui:inputText attribute specification
lightning:input attribute specification
The following attributes from your markup for lightning:input is not supported:
click,
updateOn
and keyup.
This is why it is throwing an error.
There are different attributes for handling these changes like:
...
1
Error while generating dynamic URL: The reference to entity “retURL” must end with the ';' delimiter
You cannot nest the merge fields. URL must be generated inside the single merge field {!}, and inside you can concatenate the variables and string. Following would be the psuedo code and the query parameters must be separated by ampersand sign (&):
{!'/p/attach/NoteAttach?pid=' + v.recordId +
'&parentname=' + v.simpleRecord.CaseNumber +
...
1
You should use lightning data services in the components. Lightning data services automatically captures records changes and you can get update details(like which field is updated and value of the field). After that you can utilityBarAPI to open the utility.
Code Markup - Cmp
<aura:component implements="force:hasRecordId,flexipage:...
Only top voted, non community-wiki answers of a minimum length are eligible
