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.


7

It's helpful to understand the various concepts directly. Product (Product2) Represents a product. A product is something that can be sold. For example, you walk in to a store and see packages of pencils; each package has a SKU or UPC that would be considered a Product Code. Such a product can be active or not (can be sold or not). Price Book (Pricebook2) ...


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

Try running this query in your developer org: SELECT Id, JobType, MethodName, Status FROM AsyncApexJob WHERE CompletedDate = TODAY This query will return all completed batch, future, and queryable jobs that were completed today. If you don't see your @future method in the list, then there's something wrong, but if you see a status of Completed, then ...


5

Your code is just fine, your mock class seems to be the culprit. Make sure you're returning JSON like the original, including the outer [...], which makes it a list. If the first character in your JSON is {, it will be a Map<String, ANY>. Note: Your System.assertEquals method parameters are backwards; the first value is the expected value, the second ...


5

Your trigger l ine: ServiceCredentials__c cred = ServiceCredentials__c.getValues('BillingServiceCredential'); is fetching a Custom Setting. You need to mock values of this custom setting in your testmethod. You should not rely on org data (seeAllData=true) except in the most unusual of circumstances. You can mock custom settings like any other SObject by ...


4

Change the filter criteria of field update to below one: It will resolve the issue.


4

As per Data Integration Specialist Superbadge - Step 7 issue, there appears to be an issue with the web service returning: {"timestamp":1500520484619,"status":500,"error":"Internal Server Error", "exception":"java.lang.OutOfMemoryError","message":"unable to create new native thread","path":"/ws"} Rather than the expected SOAP response. Or even a valid ...


4

The error is because the Equipment__c (Lookup to Product) is having a lookup filter. You have to find out the look up filter conditions specified on this field and make sure the product record you are linking to your Work Part record is meeting those conditions. In your code, the testEquipment1 and testEquipment2 records are being set with only 2 fields ...


4

Trailhead's message about "system mode" is a clue here: the validation checker is looking for you to explicitly declare the sharing model, which is best practice anyway. You need to add the without sharing keyword to the class declaration so it always runs in system mode, regardless of calling context.


3

While LWC is arguably a far superior framework, there are things you can do with Aura that you simply can't do with LWC. For example, dynamic creation of components simply by name. Or use of a component as an action. You can find the list of missing capabilities here (this could be a little out of date since it is a 2019 blog).


3

The field name of Picture__c has incorrect spelling in the tag - force:recordData It is currently force:recordData aura:id="service" recordId="{!v.id}" mode="VIEW" targetFields="{!v.boat}" fields="Id, Name, Description__c, ...


3

Always also pay attention to line numbers when errors occur. I presume this line is the source of the problem: List<Object> params = (List<Object>)JSON.deserializeUntyped(res.getbody()); For that line to work, the JSON would need to have an array at its root i.e. be [ ... ] but you are providing an object in your mock i.e. { ... }. See e.g. ...


3

There are several different approaches you can use to test your trigger and attempt to isolate the bugs. Manual Testing Manual testing boils down to performing record creation or update steps within the user interface (or via Anonymous Apex) that cause your trigger to run and yield you some information, whether that information comes via an exception ...


3

You can follow the directions in this article. I'm not going to copy and paste the text verbatim, but basically you want to create a new developer edition (if you don't have one yet), log a case (note, this form does not require authentication), and they'll contact you back to get the problem fixed. They also recommend linking your Trailhead account to one ...


3

JavaScript is cAsE-sEnSiTiVe. As such, your code should read: <div style="{!'background-image:url('+v.boat.Picture__c+')'}" class="innertile"> Everything in Lightning is this way. You must pay attention to the capitalization of everything you type in carefully. This includes expressions, CSS, function names, variables, component names and event ...


3

I don't think it is an import issue. I've managed to pass this part after getting some hours of sleep. There are just four required imports for this specific step and JS file. My guess is that maybe extra imports are also considered by the checking tool. Also, the checking tool seems to be a little too picky about semicolons. Always try to use semicolons for ...


3

I also experienced that error. The provided comment '// this getter must be public' is significant. Check the 'Public Properties' and 'Use Getters and Setters to Modify Data' sections in the LWC dev guide.


2

Not a bug per-se, this is exactly the point of assertNotEquals... if the parameters ARE NOT EQUAL it returns true. Else, it returns false. You answered yourself in your question: "Both the values will be same, the assertNotEqual is failing because both the values are same!" Exactly right, as it should. See the docs for more information: https://...


2

Going on the error message alone: Price Book Entry ID: id value of incorrect type: 01s..... Something is looking for a PricebookEntry ID (01u keyprefix) and is instead getting a Pricebook2 Id (01s keyprefix) Check the ID's you are putting in for the Price Book Entry ID are infact IDs for the correct record types. See also: Product and Schedule Objects ...


2

For the Field Sales User: Uncheck everything in the "Administrative Permissions" and "General User Permissions" sections other than the following: API Enabled, Chatter Internal User, Create and Customize Dashboards, Create and Customize List Views, Create and Customize Reports, Edit My Dashboards, Edit My Reports, Run Reports


2

So the issue had nothing to do with the error message reported. In order to trouble-shoot the issue I changed the PlotMapMarker.evt from 'APPLICATION' to 'COMPONENT' then hit submit on item 10. This time I received a message that the PlotMapMarker.evt wasn't configured correctly, which is as one would expect. From there I continued down the path of ...


2

JSON keys and string values should be in double quotes, try double quotes instead of single quotes.


1

NullPointerException in your own code is always something you can trace out for yourself, and it's virtually always a logic fault - not an issue with Salesforce itself. Line 35 appears to be this: Date_Due__c = Date.today().addDays(caseToShortestCycle.get(c.Id).intValue()), and sure enough, that's a top suspect for a NullPointerException. get() returns ...


1

Another important note to add is that the superbadge's scenario doesn't include the requirement to make it app hostable. So, it's worth it to remove the force:appHostable from the implements declaration.


1

In my apex class (BoatSearchResults) I had included the Geolocation__c field as part of the query. The result of this was that the callback function would always error out unless I converted the return to a JSON string then parsed the string from the component's controller. Given that the requirements do not outline including the Geolocation in the ...


1

Make sure you're in Salesforce Classic (Solutions are not available in Lightning Experience). Next, configure your categories in Setup > Customize > Solutions > Solution Categories. After that, check your page layout in Setup > Customize > Solutions > Page Layouts, edit the layout, go to the Related List section in the layout palette, and add Solution ...


1

Managed to solve this. I've removed the component from everywhere, deleted the component and recreated it with this code, added it to the Sales App utility bar and it finally worked. <aura:component implements="flexipage:availableForAllPageTypes" access="global" > <ui:outputurl aura:id="TrailheaDX" value="https://developer.salesforce.com/...


1

Salesforce cannot return a result with a Location field in it. But the Apex controller could return a JSON String: public with sharing class BoatSearchResults { @AuraEnabled public static String getBoats(String boatTypeID) { List<Boat__c> returnList; if (boatTypeID != ''){ returnList = [Select ID, Name, ...


Only top voted, non community-wiki answers of a minimum length are eligible