The independent daily for Salesforce admins, developers and architects

Curated by Abhinav (opens in a new tab)

Recommended

Fixing the field-access error in Agentforce Answer Questions with Knowledge (opens in a new tab)

You will learn the five checks to run when an Agentforce Service Agent fails with a field-access error while answering from Knowledge articles, and the order to run them in.

Why read this

The piece is a practical troubleshooting guide rather than new platform news.

  1. Assign Data Cloud User Permission Set
  2. Grant Read on Knowledge and mapped fields
  3. Enable Allow View Knowledge
  4. Verify data space access
  5. Confirm search index is Ready
The five checks to run in order when the field-access error appears

The article covers an error that appears when the Answer Questions with Knowledge action runs against an Agentforce data library: the agent’s running user cannot read one or more fields the library depends on. The usual causes are missing permissions, missing field-level security, or an incomplete Data Cloud setup. The agent runs as the user with the Einstein Agent User profile, and every object, field and Data Cloud resource the data library touches must be readable by that user.

The guide gives five checks in order: confirm the Data Cloud User Permission Set is assigned to the agent user, confirm Read access on the Knowledge object and every mapped field, enable Allow View Knowledge, verify the user’s data space access in Agent Studio, and confirm the search index for the Knowledge data library is Ready. It also recommends a dedicated Permission Set for the agent user, re-auditing field-level security whenever the library changes, granting least privilege, and testing as the agent user rather than as an admin.

The author notes that the source material contained no code, and that the link between an unready search index and this specific message is not confirmed in the source, so it should be checked as a separate cause.

Read the original at InfallibleTechie (opens in a new tab)

Worth reading?

Recommended

Setting up zero-copy V2 between Salesforce Data Cloud and Snowflake (opens in a new tab)

You will learn the setup steps for the Zero-Copy V2 connector, including the enrollment code handoff, consumer grants and legacy schema aliases.

Why read this

You will also see where change tracking via streams failed in one test.

  1. Create connector and get Enrollment ID
  2. Create Snowflake V2 target in Salesforce
  3. Link Data Share to the target
  4. Mount shared data and grant access
The V2 setup runs between the Snowflake admin and the Salesforce admin in four steps

The author revisits connecting Salesforce data to Snowflake and reports that the V2 connector simplifies setup. The enrollment code replaces manual credential configuration, authentication uses OpenID Connect, and friendly names reduce SQL cleanup. Legacy schema aliases and grant comparisons before and after migration help keep existing access intact.

The walkthrough covers creating the connector and retrieving the Enrollment ID, then the Salesforce-side steps: creating a Snowflake V2 Data Share target, linking a Data Share to it, and mounting the shares in Snowflake as a linked database. It also covers granting usage and select privileges on existing and future views to the consuming role, and the choice between legacy and friendly naming.

The author’s incremental test did not work. A stream on an exposed view failed with a change tracking error involving unmanaged Iceberg tables, so current-state queries worked but change feeds did not through that path. The author recommends confirming the supported source object and stream setup, then testing inserts, updates and deletes end to end before relying on downstream history.

Read the original at dev.to (opens in a new tab)

Worth reading?

Recommended

Agentforce Specialist exam outline updates and a four-week study plan (opens in a new tab)

Readers will learn the updated Spring 2026 Agentforce Specialist exam structure, key topic weights, and a hands-on preparation plan using Developer Edition orgs and core platform tools.

The Spring 2026 Agentforce Specialist exam has been restructured, removing separate Sales Cloud and Service Cloud sections while adding Agent Script, hybrid reasoning, Testing Center workflows, governance, and multi agent orchestration. The assessment consists of 60 scored multiple choice questions plus five unscored ones, lasts 105 minutes, requires a 72 percent passing score, and costs 200 dollars to register.

A four week preparation strategy emphasizes practical application over rote memorization. Week one focuses on prompt engineering and the Trust Layer using field generation and flex templates grounded in record data. Week two covers Data Cloud fundamentals, guiding readers to build a file based Data Library and connect policy documents to test retrieval behavior. Week three shifts to agent creation, requiring the construction of an agent with Flow backed actions and deterministic decision filters. The final week covers the Testing Center, deployment procedures, analytics, and governance monitoring.

Common study mistakes include relying on outdated outlines, underweighting the AI Agents section, treating Data Cloud as optional, and ignoring annual maintenance requirements that expire the certification. The article concludes that demonstrating configured solutions and tested agents during technical interviews carries more weight than the certification badge alone.

Read the original at dev.to (opens in a new tab)

Worth reading?

Connecting Data Cloud to Agentforce Studio to build an agentic RAG pipeline (opens in a new tab)

Readers will learn how to configure a custom retriever in Agentforce Studio, create a Flex Prompt Template in Prompt Builder, and deploy a subagent that grounds responses in live Data Cloud vector data.

The article explains how to configure a custom retriever in Agentforce Studio to fetch vectorized chunks from a Data Cloud data model object. It details setting result limits, mapping target fields, and activating the retriever so it can be referenced elsewhere.

Next, it walks through creating a Flex Prompt Template in Prompt Builder by modifying a standard knowledge template. The author shows how to add the retriever as an action, bind the query parameter, and write strict instructions that force verbatim source extraction and handle missing data gracefully.

Finally, the piece covers assembling an Agentforce Service Agent, keeping only essential routing subagents, and linking the custom Prompt Template as an action. The author validates the workflow by testing destination queries and confirming the agent returns accurate, grounded answers sourced directly from the live Data Cloud index.

Read the original at Salesforce Break (opens in a new tab)

Worth reading?

Set up Data Cloud web crawlers to ingest and vectorize external pages for AI agents (opens in a new tab)

Readers will learn how to configure a Data Cloud Web Content Connector, filter target elements with CSS selectors, and generate searchable vector chunks from live websites.

Why read this

The guide also shows how to verify the ingested data using Data Explorer and SOQL.

The article introduces Retrieval-Augmented Generation and explains why keeping AI agents grounded in real-time data matters. It outlines the prerequisites of enabling Einstein, Agentforce, and Data Cloud in a development org.

It details the configuration of a Web Content Connector in Data Cloud Setup. The steps explain how to set crawl depth to zero to avoid following irrelevant links and how to use browser developer tools to copy CSS selectors for targeting specific page elements.

The guide describes creating a Data Lake Object and its corresponding Data Model Object. It notes that semantic search must be enabled while skipping image embedding and knowledge harmonization for this text-only use case. It concludes by showing how to validate the chunked output through Data Explorer and standard SOQL queries against the unstructured data model object suffix.

Read the original at Salesforce Break (opens in a new tab)

Worth reading?

Must-read

Advanced PySpark patterns for batch data transforms in Data 360 (opens in a new tab)

Readers will learn how to structure, test, and deploy PySpark Code Extension scripts for complex batch transformations in Data 360.

Why read this

The piece demonstrates three production-ready patterns for hierarchical rollups, JSON event parsing, and machine learning scoring.

  1. Author PySpark script locally using Python SDK
  2. Validate script locally via SF CLI command
  3. Deploy packaged extension to Data 360 org
  4. Execute managed Spark job on demand or schedule
The end-to-end workflow for developing custom batch transforms in Data 360

The article introduces Data 360 Code Extensions as a mechanism to run custom PySpark logic against Data Lake Objects and Data Model Objects within an isolated compute environment. It outlines the full development lifecycle, detailing how engineers use the Salesforce Command Line Interface to validate scripts locally against a sampled dataset before packaging and deploying them to the platform.

The first example implements an iterative loop to calculate total tree revenue across variable-depth account hierarchies by continuously joining frontier records until convergence. The second example provides a reusable helper to parse and explode JSON array columns containing batched session events into individual rows for downstream analytics.

The third example demonstrates how to bundle a serialized scikit-learn classifier and its categorical feature grid to score leads efficiently via a broadcast join. The post concludes by reviewing managed Spark constraints around memory and timeouts, while noting that the transformed outputs become queryable objects for Agentforce agents.

Read the original at Salesforce Developers Blog (opens in a new tab)

Worth reading?