#Trailhead484 discussing

Hello @Sam van Rooij

make sure you have typed in correctly all values (or copy-paste'd them). The focus is on Name, Industry value and number of employees. It is often the number of employees that is incorrect (1000 or 100000, instead of 10000). 

If that does not help, make sure that both your Trailhead page (it seems from your screenshot that this is the case) and your playground are in english. 

Eric

Hi Suraj,

To write a unit test for a @future (callout=true) method, you need to mock the HTTP callout (using HttpCalloutMock) and enclose the execution between Test.startTest() and Test.stopTest(). Salesforce runs all asynchronous methods (like future methods) called within startTest() and stopTest() synchronously right when Test.stopTest() executes. 

Here is an example test class structure to cover your method:

1.Create a Mock Callout Class:

Mock Implementation. 

Create a mock class that implements HttpCalloutMock to return a fake JSON response simulating your patchCall output (ensuring it contains 'state' => 'Success' and a valid JSON structure with an id field).

2.Prepare Test Data and Context:

Test Setup. 

In your test method, insert a test Bid_Review_Request__c record so that the update brUpdate; statement can successfully find and update a record in the database.

3.Wrap in Start/Stop Test:

Execution and Assertion. 

Assign your mock, wrap the future method call inside Test.startTest() and Test.stopTest(), and assert that the record was updated successfully.

Apex 

@isTest
private class NewProjectHandlerTopUpTest {
    // 1. Mock class for HTTP callouts
    public class MockHttpResponseGenerator implements HttpCalloutMock {
        public HTTPResponse respond(HTTPRequest req) {
            HttpResponse res = new HttpResponse();
            res.setHeader('Content-Type', 'application/json');
            res.setStatusCode(200);
            // Construct JSON response matching the parser requirements
            res.setBody('{"state": "Success", "resBody": "{\\"id\\": \\"12345\\"}"}');
            return res;
        }
    }
    @isTest
    static void testNewProjectHandlerTopUp() {
        // Create test record to satisfy update operation
        Bid_Review_Request__c testReq = new Bid_Review_Request__c(
            Name = 'Test Project'
            // Add required fields for Bid_Review_Request__c here
        );
        insert testReq;
        Map<String, String> recordMap = new Map<String, String>{
            'ID' => testReq.Id,
            'Name' => 'Test Project'
        };
        // Set mock callout
        Test.setMock(HttpCalloutMock.class, new MockHttpResponseGenerator());
        Test.startTest();
        // Calling the future method
        YourClassName.newProjectHandlerTopUp(recordMap, '{"test":"json"}', 'destination', 'WBS123');
        Test.stopTest(); // Future method executes here
        // Assertions to verify the record was updated
        Bid_Review_Request__c updatedReq = [SELECT WBS_Project__c FROM Bid_Review_Request__c WHERE Id = :testReq.Id];
        System.assertEquals('12345', updatedReq.WBS_Project__c, 'The WBS Project code should be updated successfully.');
    }
}

(Note: Replace YourClassName with the actual name of the Apex class containing your future method).

Hi Mohammed,

Looking at your screenshot, the error message reads: "The 'Solarbot Pipeline by Stage' component is the incorrect size or in classe incorrect position."

In Salesforce Lightning Dashboards, the automated checker strictly verifies the exact grid dimensions (width and height) and coordinate placement of each component. Based on your layout, the SolarBot Pipeline by Stage component is currently positioned spanning across the left side, but its height or column span does not match the precise specifications required by the superbadge instructions.

1.Open Dashboard Builder:Dashboard Layout. 

Open the SolarBot Impact Dashboard in Edit mode. You can verify success when you see the grid configuration handles on your dashboard components. 

2.Adjust Component Width and Height:Component Sizing. 

Click and drag the corners of the SolarBot Pipeline by Stage component to match the standard sizing and layout guidelines specified in the superbadge instructions (typically a specific number of columns wide and rows high, ensuring it aligns symmetrically with neighboring components). You can verify success when the component grid boundaries snap to the correct layout proportions. 

3.Save, Refresh, and Re-run:Save and Check. 

Click Save, refresh the dashboard view, return to Trailhead, and click Check Challenge. You can verify success when the green completion checkmark appears.

Hi Vruttika, the error indicates that the Salesforce CLI is not detecting a valid DX project in the current directory. 

From your screenshot, the terminal is running from:

D:\Salesforce\geolocation

First, make sure this folder contains sfdx-project.json. You can verify with:

dir sfdx-project.json

If the file is in a different folder, use cd to navigate to that folder and then run the command again.

For example:

cd D:\Salesforce\geolocation
sfdx force:source:push

Also make sure sfdx-project.json is valid and that you're opening the project root folder in VS Code, not a parent or child folder.

If it still gives the same error, please share the contents of sfdx-project.json and the output of dir, so we can check whether the project structure is correct. 

Hi Guilherme, Custom Keys aren’t required for basic push notifications. They’re used when the app needs to receive additional key-value data in the push payload, for example to support tracking, deep linking, or custom app behavior. The mobile app code needs to be implemented to handle those keys. 

For the basic MC Next setup, you’ll need to configure the mobile app and the appropriate iOS/Android push service credentials, then configure the SDK in the app to receive push notifications. 

So if the implementation doesn’t require any custom data or app-specific behavior, Custom Keys generally aren’t necessary. If you share what the other company is asking you to configure as the Custom Keys, it may be easier to determine whether they’re actually needed. 

Hi Prashant,

The validation error message states: "In the Predicted Conversion model, Autopilot has not been disabled."

In Model Builder (Einstein Studio / Data Cloud), Autopilot is often enabled by default when creating a model configuration. To disable it, you need to locate the advanced settings or configuration toggle during model creation/editing. 

1.Open the Predicted Conversion Model:Model Navigation. 

Launch your Predictive Models Playground org, navigate to Model Builder, and open your existing Predicted Conversion model configuration. You can verify success when you are viewing the model's setup details page. 

2.Locate and Turn Off Autopilot:Configuration Settings. 

Look for the Autopilot toggle or configuration option (typically found in the model settings, provider setup, or advanced training configurations). Toggle or switch it to Disabled. You can verify success when the Autopilot setting shows as turned off. 

3.Save and Re-run the Challenge:Save and Check. 

Save your changes to the model, return to Trailhead, and click Check Challenge to Earn 500 Points. You can verify success when the green completion checkmark appears.

It's been a long time since I've done that Challenge.   

I think you're supposed to select the Account record for "Edge Communications" and then click the Gear icon and then Edit Page