Salesforce Winter '27 for Agentforce and Data 360: What Actually Changes
Waves land 4 Sep, 2 Oct and 9 Oct 2026. Why the Data 360 section looks thin, what the Agentforce renames signal, and the deprecations that actually break things.
Async Apex, bulk design and performance at volume — the code that works on ten records and dies on ten million.
Designed and created by Salesforce Expert
10 sections · 56 lectures · 17 hands-on labs
This course opens on the night a rating run did not finish, and everything after it is about why. It is the Apex course for code that has to survive volume: what a transaction actually costs, trigger design at scale, transactional integrity when things fail halfway, asynchronous Apex done properly, selective SOQL against large data volumes, dynamic Apex, platform events, and integration in both directions.
It assumes you can already write Apex. What it adds is the judgement to look at a working class and see where it will fall over in eighteen months, and the techniques to measure that rather than guess.
Waves land 4 Sep, 2 Oct and 9 Oct 2026. Why the Data 360 section looks thin, what the Agentforce renames signal, and the deprecations that actually break things.
Four ways to ground an agent in Data 360, when each is right, and why zero-copy federation is the wrong choice for the retrieval path of a live conversation.
Every Agentforce project has this argument in week three. The rule that sorts deterministic steps from generative ones, and why each half needs a different test.