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.
Reports that are correct and dashboards somebody actually opens — including how to show a trend in an org that keeps no history.
Designed and created by Salesforce Expert
7 sections · 22 lectures · 6 hands-on labs
Two people run a report on the same dataset and get two different answers. That is the problem this course is about. It starts before the report builder — with getting the question — and then covers reports that are correct, the perennial problem of showing a trend in an org that keeps no history, dashboards that get opened, and who is allowed to see which number.
It ends with the estate: what happens when an org has four hundred reports and nobody knows which are trusted. It deepens the Data and Analytics Management domain of the Platform Administrator exam and carries no exam of its own.
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.