3
Your code has a number of typos. Notably, JavaScript and Lightning are cAsE-sEnSiTiVe. This means that aura:Handler should be aura:handler, Sortable should be sortable, newDeaths should be NewDeaths, etc. You need to review your code to find any other characters that are incorrect. Check the documentation if you're not sure. You also have some spelling ...
3
It is not correct that Salesforce will withdraw Aura Component stuff (Its not documented anywhere so unless you see in any official docs its not true). Salesforce supports both the programming model (Aura and LWC) and you can always use LWC inside aura components while other way round is not possible.
Salesforce has excellent documentation on when to choose ...
3
In Order to create a component dynamically from JS, you need to declare the component a dependency in component markup
Test.cmp
<aura:component >
<aura:dependency resource="markup://c:sample" />
<aura:handler name="init" value="{!this}" action="{!c.doInit}"/>
{!v.body}
</aura:component>
TestController.js
({
doInit ...
2
it is expected behavior. please check documentation Navigation
Experience Lightning Experience, Lightning Communities, Salesforce
Mobile App
it will not work for Lightning Out (embedded in VF page)
2
Full table scans are a bad idea, which is what you get with a LIKE. Even if you had only 1, you'd be dealing with relative slowness. Use two or three queries instead. First, SOSL for all Orders where Project_Id__c matches the search term. Next, SOSL for all Accounts that match any of the three fields. Third, SOQL to get any orders that match those results.
...
1
There is a typo in the expression you are testing
it should be {!v.runningUser.ProfileId} and not {!v.runningUser.profileId}
Correct code:
testId-->{!v.runningUser.ProfileId}
<br/>
rb --> {! equals(v.runningUser.ProfileId, '00e1o000001EImgAAG')}
<br/>
wrd--> {!notequals(v.runningUser.ProfileId, '...
1
Take a look at Business Hours. That's probably something you need.
You can find them in Setup -> Business Hours.
1
It's not so obviously on one screen (though you could build something), but they are Business Hours and Holidays. Salesforce provides the ability to calculate times based on these support hours (e.g. "SLA is 20 business hours, when does that elapse given store hours?"), and can be used in Apex as well to support custom code that leverages this information.
1
if SFSY is a checkbox, then you can't compare strings
Instead of this
if(SFYI == "true") {
You should do
if (SFYI) {
That is the simplest way of checking whether a variable is true or not
1
In Aura, you can use a Promise to wait for the result. That would look like this:
callHelper: function(component,event,helper){
helper.createRecord(component,'dum1')
.then(function(result) {
console.log(result);
});
}
createRecord: function(component, recordName) {
return new Promise(
$A.getCallback(function(resolve, reject) {...
1
Your Apex action is called asynchronously from helper.createRecord(). It does not execute until after createRecord() itself returns, so it's not possible to synchronously return its result value to the calling method, callHelper() - and you certainly wouldn't want the code that's running in your UI to block waiting for an asynchronous function to return, as ...
1
JavaScript is pervasively case-sensitive.
aura:id='CarSearchResult' != component.find('carSearchResult');
Use consistent casing and this basic structure should work, assuming that there is exactly one component with this aura:id.
1
Personally, I'd advise using a "wrapper" to glue everything together.
<aura:attribute name="questions" type="Map[]" />
<aura:iteration items="{!v.questions}" var="item">
<lightning:input aura:id="question" type="{!item.Type__c}" name="{!item.question.Name}" label="
{!item.question.Label__c}" value="{!item.answer.Value__c}" />
<...
1
When you look at lightning-navigation, you'll see it's only supported in:
Lightning Experience, Lightning Communities, Salesforce Mobile App
Notably, it is not supported in Lightning Out. You'll need to come up with a different approach.
Only top voted, non community-wiki answers of a minimum length are eligible
