#New Releases30 utenti parlano di questo argomento

Hi Fabian, 

Two separate reasons, per official Winter '27 release notes: 

1. "Compare Values Between Fields in SOQL" (FORMULA() in WHERE clauses): requires API version 68.0+, and is scoped to sandboxes/Developer Editions/scratch orgs only. If your sandbox's API version isn't bumped to 68.0+ yet, it won't show even on Winter '27. 

2. "Preview Records from Lightning Reports Without Losing Context": ships as Beta with Salesforce's standard disclaimer that beta features aren't guaranteed to roll out simultaneously with GA features, even within orgs already on the release. Some Winter '27 betas explicitly require Salesforce Support to switch on (e.g., "Show Only Matching Records Across Blocks in Joined Reports" says exactly that), so it may need manual enablement rather than a Setup toggle you're missing. 

Reference:

Next step: confirm your sandbox's API version for #1, and if #2 still doesn't appear, open a case with Support to check if it needs manual enablement on their side.

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 Pedro, you can search for other Trailblazer Community members by using the search bar in Trailhead and selecting the People/Members results. 

You can also open a member’s profile from their posts or comments and use the available profile options to connect or follow them. 

If you’re not seeing the member search option, could you share a screenshot of what you see? The Community experience has changed over time, so the available options may depend on the version of the site you’re using. 

Hi Branden, if the new picklist values are already added to the relevant Record Types but still aren’t showing, I’d also check the field-level configuration and confirm the values are Active.

Also verify that you’re testing with the expected Record Type and that the picklist field isn’t being restricted by a dependent picklist or another configuration. 

If it still doesn’t appear, could you share the picklist field, Record Type, and a screenshot of the Picklist Values and Record Type settings? That would help narrow it down. 

Hi Raj, you can check this from Setup → Release Updates and look for “Enforce OAuth Scope for Lightning Apps.”

To test whether your org is impacted:

1. Test the release update in a sandbox first.
2. Open the release update and click View Details / Get Started.
3. Test any Lightning or Lightning Out apps that use OAuth authentication.
4. Check Setup → Login History for OAuth logins where Login Type = Remote Access 2.0 and review the Application column for the connected app being used.
5. Cross-reference those logins in Session Management, particularly sessions with Session Type = Aura.
6. Review the OAuth scopes configured on the relevant Connected Apps. The scope should provide the access required by the Lightning app, such as lightning, visualforce, web, or full when necessary.

Salesforce specifically recommends testing Lightning and Lightning Out applications in a sandbox before enabling/enforcing the update.