13
I was able to recreate the issue, and although I don't know what is causing it, I was able to get past it by changing the name of the apex class:
public class MyContactListControllers {
@AuraEnabled
public static List<Contact> getContacts() {
return [Select Id, Name, Email, Title, Phone From Contact];
}
}
and then making the ...
10
I ended up moving the createItem function from my helper function to the CampingListController, since Trailhead does not "ask" us to split the createItem into a helper function.
handleAddItem: function(component, event, helper) {
var addItm = event.getParam("item");
helper.createItem(component, addItm);
},
createItem: function(component, ...
10
You might be able to use MyTrailhead for this sort of thing. Not sure if it is yet Generally Available or how much it will cost.
10
That's Earnie Badger.
Earnie was introduced on Salesforce's Official Blog:
How do you see the Trailhead brand? Who are the main characters?
[...] Earnie Badger was made for our community of passionate badge-earners. [...]
10
UPDATE
Just got an update that the Spring '19 pre-release signup link is now live. You can access it on this link.
You are getting this error because the LWC project expects a version 45.0 (Spring '19 pre-release org), whereas the current DE sandboxes are still on version 44.0 (Winter '19).
You will need to signup for the Spring '19 pre-release DE Org to ...
9
Update:
As of December 15th 2017, the final two superbadges; Lightning Component Framework Specialist and Advanced Apex Development are now available so you can complete your PDII journey and get your hands on your well-deserved Platform Developer II credential!
At this stage the best public information on the remaining two super badges is:
The other two ...
8
The collection newlyCreatedCases is static in the class MaintenanceRequestHelper. That means it will exist for the entire execution context and across all the trigger invocations.
Each trigger invocation will work with a maximum of 200 records. So up to the first 200 records you won't notice any difference. At 201 records the trigger will be called twice. ...
8
I believe the error is in reading the requirement. You're changing the value of ALL Adventure Packages, not just the one related with the Fulfillment. You probably need to use the Product as a filter.
8
Use single-quotes (which is a Prettier setting).
7
This is the step by step approach for this implementation.
Animal
public class Animal {
public Integer id;
public String name;
public String eats;
public String says;
}
AnimalResult
public class AnimalResult {
public Animal animal;
}
AnimalLocator
public class AnimalLocator
{
public static String getAnimalNameById(Integer id)
{
...
7
Thank you for the feedback and sorry our content was not clearer about how to set up Java for Salesforce Extensions for Visual Studio Code.
We have some better instructions coming in new content in the March release, but I'll make sure we get the instructions centralized and referenced from other content using VS Code, like the Lightning Web Components ...
7
This is a timing issue. After setting up the
Dev Hub playground
Packaging Playground
and enabling the Dev Hub in the Dev Hub playground ...
you may need to wait a few minutes for the credentials to propagate in the SFDC backend. For me, it was the length of time to
Google around to see if this error had been previously reported
Log off/login and try ...
6
The query in this line is not returning an Account:
Account result = [SELECT Id, Name, (Select Id, Name from Contacts) FROM Account WHERE Id = :AccId];
This is happening because the variable AccId is null.
To get at the heart of your problem, the string method that you are using, substringBetween(), evaluates its parameters as case-sensitive. The C ...
6
I had the same issue.
Seems the Trailhead Validation engine is looking only for the Day in US timezone
My Dev Org is in AP instance and my user timezone is in ANZ, so the day returned in the formula is usually a day ahead of the day in US.
The only way I could get thru is to return the previous day for my current timezone and it worked.
I've posted ...
6
Based on the fact that comparator has a public set and that you don't actually set the value anywhere in your code, I'm going to guess you pull this value from a user input on the page (you didn't share your markup). Same goes for numberOne.
Even if you use a picklist, set the input type to number, etc. the value sent back to the server can be manipulated, ...
6
You declared your return type as void. Change it to List<String>.
Incorrect
public static void generateStringArray
Correct
public static List<String> generateStringArray
It would be worth your time to read up on Class Methods:
To define a method, specify the following:
Optional: Modifiers, such as public or protected.
Required: ...
6
Javascript is case-sensitive.
action.setCallBack is not a function because setCallBack should be:
setCallback
If you read the documentation from the Lightning developer guide, this is specified:
Expression Functions Reference
The expression language contains math,
string, array, comparison, boolean, and conditional functions. All
functions ...
6
That would be Appy. Below is a link to all the mascots.
https://www.salesforce.com/blog/2017/07/meet-trailhead-characters.html
6
The answer is in the comments, however, here are the details of the error. It looks like there is a problem with serializing Apex objects to JSON.
Calling server controller method, I get the following response:
while(1);
{"actions":[{"id":"578;a","state":"SUCCESS","returnValue":[{"BoatType__c":"a011N00000ULFDXQA5","Contact__c":"0031N00001J1joRQAR","...
6
That must be Earnie, the new female badger. Heard about her the other day from someone in marketing., but she represents getting badges on Trailhead.
6
Yes, you will get the 101 query exception1.
The reason is that all of the trigger "chunks" (I prefer using "chunk" over "batch", because "batch" in Salesforce is a separate thing) are part of the same transaction, and governor limits are enforced per-transaction.
If you use one query in your trigger, then your trigger can handle (at most) 20,000 records.
...
6
The reason that your test method can't see your operational method is because your operational method was declared as private.
private
This is the default, and means that the method or variable is accessible only within the Apex class in which it is defined. If you do not specify an access modifier, the method or variable is private.
Your test method is ...
5
I answered this question in this thread. You should post Trailhead related questions in the Trailhead forum for faster assistance.
5
I spend some time digging deep into why I could not assign a Permission Set to multiple users within my DE org (Developer Edition) to come to the realization that these users were inactive within the environment.
I just want to post this as an answered question incase anybody else has this issue.
5
At the time I did it, I used this line of code and it worked. That's true it's not clear in the Trailhead module how to do it.
component.set("v.newItem", "{'sobjectType':'Camping_Item__c','Name':'',Quantity__c': 0,'Price__c': 0}");
5
Go to your Profile
At the bottom right of the page you can change your language
5
The challenge mentions "Create a display component named accDisplay.cmp using the record attribute named accountRecord", however you're using the attribute named simpleNewAccount.
Try to use the correct attribute name and it should be ok.
5
Yes, you can "merge" your existing account to a new account. Note that the change is irreversible. See this answer for more info, but I'll include the essential text here.
Before We Begin
The following process assumes that the learner can still log into both
the ‘from’ and ‘to’ Trailhead accounts. If the learner can no longer
access the ‘from’ ...
5
You have issue in aura:handler. It will be
<aura:handler name="addItem" event="c:addItemEvent" action="{!c.handleAddItem}" />
instead of
<aura:handler name="addItem" event="c.addItemEvent" action="{!c.handleAddItem}" />
5
Seems 100% like a your EmailManager failed to compile. Normally you would see errors similar to this one if you declared your method static and called it the way you did:
// won't work, can't call static method from instance
public class MyClass
{
public static void myMethod(/*params*/) { /*implementation*/ }
}
// script
new MyClass().myMethod(/*params*...
Only top voted, non community-wiki answers of a minimum length are eligible
