The independent daily for Salesforce admins, developers and architects

Curated by Abhinav (opens in a new tab)

Informatica adds governed enterprise data to Copilot, Foundry and Fabric (opens in a new tab)

You will learn what Informatica's Microsoft integrations now provide: Copilot access to business context, MCP-based governance for Foundry agents, and broader Fabric lineage scanning.

Why read this

You will also see the new U.S. East Coast Azure deployment option and what is generally available.

  1. Informatica governance and lineage data
  2. Headless MCP servers and scanners
  3. Microsoft Copilot, Foundry and Fabric
  4. Governed AI agents and analytics
How Informatica trusted data reaches Copilot, Foundry and Fabric agents

Informatica from Salesforce has expanded its collaboration with Microsoft, announced at Microsoft Ignite 2026. The integration brings Informatica’s enterprise data intelligence into Microsoft Copilot and Teams, giving business users access to business definitions, data quality, governance and lineage through natural-language experiences. The article presents this as a response to the gap between agents that can access data and agents that understand it and operate within access policies.

For AI developers, the integration with Microsoft Foundry extends Informatica Headless MCP servers, which reached general availability earlier, with new governance, identity and administrative capabilities. These let developers ground agents in authoritative definitions, quality indicators and lineage, apply access controls, and trace agent interactions with data management services. Informatica’s MCP services are also being expanded across Azure-based IDMC points of delivery worldwide.

For data engineers and analysts on Fabric, Informatica’s scanners now cover notebooks and data pipelines as well as data at rest. The enhanced scanners provide lineage across multistep pipeline orchestrations, support impact analysis, and are administered through a consolidated interface. The article also announces a new U.S. East Coast Azure point of delivery for customers with data residency or procurement requirements, and notes that Informatica purchases through Microsoft Marketplace can count toward a Microsoft Azure Consumption Commitment.

Availability is staggered: the Copilot integration is generally available, the Foundry MCP server integration is generally available with its expanded capabilities, the Fabric scanners are generally available for notebooks and pipelines, and the Azure U.S. East IDMC point of delivery is generally available. The piece is largely promotional, with customer and executive quotes, so the technical detail on the MCP governance features is thin.

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

Also told by Salesforce Time (opens in a new tab)

Worth reading?

Recommended

Mining OpportunityHistory with pandas to see how sales really run before automating (opens in a new tab)

You will learn how to turn the OpportunityHistory object into an event log and use pandas to find stage variants, skipped stages, waiting times and single-person bottlenecks.

Why read this

You will also see what these findings should settle before an AI agent is given the sales process.

  1. Export OpportunityHistory as an event log
  2. Build stage variants and count rework
  3. Measure median wait between stages
  4. Count who moves the stages
The four analyses used to measure the real sales process from OpportunityHistory

The author argues that a documented sales process often differs from the one a company actually runs, and that an AI agent will faithfully follow whichever version it is given. Before automating, teams should measure the real process. Salesforce already records a row in OpportunityHistory whenever an opportunity’s stage, amount or close date changes, so no setup is needed. A SOQL query selecting the opportunity ID, stage, amount, close date, creation date and creator over the last 180 days can be exported to CSV and used as an event log.

The post then walks through four analyses in pandas. The first removes rows that are not real stage changes and counts the distinct stage paths, or variants, across opportunities; the documented process is usually one line, while the data usually shows many. The second flags opportunities that went back to an earlier stage and those that moved from creation to the last stage in two steps or fewer, which suggests the CRM was updated only at the end. The third calculates the median wait between each pair of stages to locate handoffs or approvals that happen outside the system. The fourth counts how many stage changes each user made, since one or two users moving most records suggests updates are being collected elsewhere and typed in.

The author stresses that these numbers show where the problems are, not why they occur. Each signal should prompt a question: which process is the real one, what the rep gains from updating the CRM, which area owns a slow handoff, and where the information actually lives. Answering these first prevents an agent from speeding up the wrong steps. The same approach can extend to orders, invoices and payments when the ERP lives in the same Salesforce org.

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

Worth reading?

Recommended

Setting up proactive Intelligence in Tableau Next with Slack and MCP (opens in a new tab)

You will learn the setup path for Tableau Next's three proactive features: autonomous insights, data alerts and intelligence briefs.

Why read this

You will also see how admins scope agents and users, and how alerts are created and managed through Slackbot.

  1. Set up Tableau Agent in Tableau Next
  2. Connect Slack to Salesforce
  3. Enable Tableau Next MCP server for Slackbot
The one-time admin setup that connects Tableau Next to Slack and MCP

Proactive Intelligence in Tableau Next has Tableau Agent monitor business data in the background and push prioritized insights to Slack, Salesforce or any MCP-compatible client. The article describes three capabilities that work together: autonomous insights, which explore data for risks nobody thought to ask about; data alerts, which notify on conditions such as a commit drop or a large deal slipping; and intelligence briefs, which run scheduled or on-demand reviews of core KPIs. All three draw on the governed semantic model so calculations follow the organisation’s definitions.

Setup is a one-time admin task. Prerequisites are Tableau Next in Enterprise, Performance or Unlimited edition, at least one AI-ready semantic data model, and Slack with the Salesforce app and Slackbot connected to MCP. The admin sets up a Tableau Agent, connects Slack to Salesforce, and enables the Tableau Next MCP server for Slackbot. For autonomous insights, the admin turns on the feature under Administration settings, scopes the agent to semantic models, creates an Agentforce Studio skill that supplies business context without scripting output, grants the AI Skill User Permission Set, and assigns an agent to each user, since no one receives insights until that step is done.

Alerts can be created in plain language through Slackbot, or through built-in metric alert types such as period-over-period change, unusual change, goal and threshold. Alerts check daily or weekly and notify only when the condition is met. The article recommends a phased rollout: start with one key alert, pilot autonomous insights with a small group of leaders, then automate one recurring review with an intelligence brief.

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

Worth reading?

How Salesforce cut lead assignment to 20 seconds using Data 360 scoring (opens in a new tab)

You will learn how Salesforce built lead scoring and three-way routing on a unified Data 360 profile, and which design choices carried the gains.

Why read this

The piece also gives a practical checklist for applying the pattern at a smaller scale.

  1. Match to unified profile
  2. Classify job level and score
  3. Apply team thresholds
  4. Route to sales, nurture or agent
Each inbound response is matched, scored and sent to one of three routes

Salesforce’s sales team routed leads across three systems with heavily customized rules, and routing changes often went live weeks late. The team unified signals such as website activity, event attendance, email engagement, support history and product usage in Data 360, then built scoring and routing on that profile. Its in-house data science team built a lead score from 1 to 5 and a product interest score, and each inbound response is matched to a profile, classified by job level, scored, and sent to a sales team, marketing nurture or agent-first outreach.

The article reports that lead assignment fell from 20 minutes to 20 seconds, custom code dropped 90% from about 2 million lines, and routing changes now take days instead of four weeks. Thresholds sit in configurable tables rather than code, so a business user could raise the bar for Tableau leads without a release. The authors credit the whole implementation for these results, not Data 360 alone, and note that the same profile drives an email journey with a 233% higher click-through rate than their average Marketing Cloud journey.

The closing advice is to unify data before scoring, define what sales-ready means for each team, give every lead a destination, and keep rule changes out of code releases.

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

Worth reading?

Eight practices for building a performant Tableau Semantics model (opens in a new tab)

You will know how to structure a Tableau Semantics model for query speed, correct joins, governance and scale, and which build path suits your situation.

Why read this

The piece is practical guidance rather than a release announcement.

  1. Business-driven design and conceptual modeling
  2. Choose a build path
  3. Implement and test iteratively
  4. Design for query performance
  5. Centralize security and standardize
Five groups of practices for building a performant semantic model, in the order the article presents them

The article argues that a semantic model should reflect business concepts rather than database schemas, and that conceptual modeling and stakeholder review should come before joins are configured. It describes three build paths: generating a model from natural language with Tableau Agent, generating one from existing CRM Analytics or Tableau Cloud data, and extending a verified model through composable modeling. It recommends starting from the Salesforce Customer 360 Semantic Model where applicable.

For performance, the guidance is to keep runtime joins to about six or seven, avoid many-to-many joins and expensive operators such as BETWEEN, join on primary keys, set explicit join cardinality, and align default filters with Data Lake Object partitioning. Secondary indexes and pushing heavy transformations upstream into Data 360 batch transforms or Calculated Insights are suggested for very large datasets. Security should be enforced through Data 360 Policies rather than model filters, which are meant for business relevance and can be bypassed by ad-hoc queries.

The piece also advises testing with the Test Model feature and visual checks for join fan-outs, and stress testing against production-scale volumes and concurrent query patterns before rollout.

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

Worth reading?

Data 360 connects to Snowflake through Zero Copy without moving data (opens in a new tab)

You will learn what the Zero Copy v2 connector exposes in Snowflake, which pieces are generally available versus in preview, and how governance and private connectivity are handled across the two platforms.

  1. Connect enterprise data
  2. Give it shared meaning
  3. Turn it into trusted context
  4. Act on it in agents
Data moves from enterprise data to action in four stages, as the article frames Data 360's role

Salesforce describes Data 360 as a context layer for AI agents, and presents its Zero Copy partnership with Snowflake as the way to reach governed data where it already lives rather than copying it through ETL pipelines. The article reports more than 1,000 joint customers running workloads with native Zero Copy, and presents this as the basis for Agent Context Engine, which combines structured data, unstructured content, knowledge graphs and agent memory.

The technical changes are the substance here. The v2 Zero Copy connector presents Data 360 objects as native Apache Iceberg tables inside a customer’s Snowflake account, queryable with SQL and usable with Streams and Dynamic Tables for near real-time change capture. OpenID Connect authentication secures access. Expanded Zero Copy with Horizon Catalog adds direct file federation with Snowflake-managed Iceberg tables, and Data 360 Private Connect Multicloud allows Data 360 on AWS to reach Snowflake on Azure without public internet traffic.

Availability is staged. The v2 connector and Private Connect for Snowflake on Azure are generally available, Expanded Zero Copy with Horizon Catalog and Snowflake Cortex Agents are in public preview, and the Salesforce and Informatica MCP servers in Cortex are in private preview. Tableau support for Snowflake semantic views is planned for general availability in early 2027.

Read the original at Salesforce Blog (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

Cutting Data 360 credit costs through ingestion choices (opens in a new tab)

You will learn how Data 360 credits are consumed by rows processed, and how the choice between zero-copy, batch and streaming, and query or file federation changes that cost.

Why read this

You will also see when internal CRM pipelines are free.

Zero-copy

  • About 70 credits per 1 million rows
  • Best for infrequent or ad-hoc queries
  • Data must stay in external lake

Standard ingestion

  • 500 to 2,000 credits per 1 million rows
  • Cheaper for frequent queries and transforms
  • Copies are acceptable
Zero-copy and standard ingestion differ in cost per million rows and in when each is cheaper

Data 360 credit consumption for many usage types is driven by the number of records processed or accessed, not by the rows returned. The article argues that pipelines which scan large volumes but return few rows waste credits, so architects should decide how data enters the platform before anything else. Data kept outside the platform, or filtered before ingestion, incurs no processing cost, and zero-copy avoids replicating data at all.

The article compares zero-copy with standard ingestion. Zero-copy suits infrequent or ad-hoc queries and data that must stay in an external lake, at roughly 70 credits per million rows processed plus compute on both sides. Standard ingestion, at 500 to 2,000 credits per million rows, is more economical when data is queried frequently and transformed. Streaming costs more than batch because of continuous micro-batching and index updates, so batch should be used unless near-real-time freshness is needed. Core CRM pipelines from Sales Cloud, Service Cloud, Marketing Cloud and B2C Commerce have consumed zero credits since August 2025, though some Industry Cloud connectors still incur standard usage.

For zero-copy, the article contrasts query federation over JDBC, which bills compute on both Data 360 and the external source and is best for datasets under 100 million rows, with file federation over Apache Iceberg, which reads storage directly, is faster on datasets over one billion rows, and has native change capture and Flow automation. It recommends enabling acceleration for frequently queried zero-copy data to avoid repeated external compute charges.

Read the original at Salesforce Architects (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?

Recommended

Deploy Python Code Extensions for complex Data 360 batch transformations (opens in a new tab)

You will learn how to structure, validate, and deploy Python scripts as managed Code Extensions within Data 360.

Why read this

The guide also covers connecting these scripts to batch data transforms and monitoring execution through the platform.

Northstar Outfitters faced inconsistent product data across commerce systems and needed a trusted catalog. Native visual transforms could not handle the required standardization, enrichment, and scoring logic, prompting the use of Data 360 Code Extension to run modular Python and PySpark scripts directly on Salesforce infrastructure.

The solution relies on isolated runtime environments where scripts read from and write to designated Data Lake Objects using explicit permissions defined in a configuration file. Developers validate logic locally against sampled data before packaging the script, dependencies, and tests into a deployable archive.

The guide details both Setup interface and Salesforce CLI workflows for uploading packages, selecting compute sizes, and linking the extension to a batch data transform. Execution, scheduling, and logging are handled by the platform, while operators can trigger runs and review history through REST API calls.

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

Worth reading?

Recommended

How Data 360 compiles governed context for artificial intelligence agents at production scale (opens in a new tab)

Readers will understand how the Agent Context Engine retrieves, reconciles, and packages authorized evidence into token-efficient Context Packs for AI agents.

Why read this

The piece also explains how Data 360 separates runtime state from durable memory to maintain governance across models and channels.

Salesforce Engineering describes how Data 360 assembles governed, authorized context for AI agents without loading an entire enterprise data estate into every prompt. The core challenge is identifying the requester, purpose, authority and freshness needs, retrieving evidence from structured and unstructured sources, reconciling conflicts, and applying access, masking, residency, consent and purpose controls, all within token, latency, freshness and cost budgets. Data 360 serves as a shared runtime foundation across Salesforce, platforms such as Databricks and Snowflake, operational systems and knowledge bases, with data kept authoritative where it lives through ingestion and Zero Copy. The article cites Q2 FY27 production usage of 104.3 trillion connected records, including 81.5 trillion Zero Copy rows.

The Agent Context Engine works in two directions. On the outbound path it moves through six runtime stages: Resolve (identify requester, agent, purpose, authority, entities and freshness), Plan (choose access paths such as relational, search, graph, RAG, streaming and federated), Reconcile (rank evidence while keeping conflicts visible), Govern (apply controls before retrieval or action), Compile (fit evidence, working state, memory and citations into a token-fit Context Pack and action contract), and Learn selectively (return typed interaction traces and decide what to promote, update or expire). On the inbound path, conversations, tool calls, decisions and outcomes return as traces for audit and evaluation. Only approved facts move into durable memory, and only validated outcomes become learnings.

Data 360 separates runtime state into four forms: working context for the current reasoning step, short-term memory for the active trace across turns, long-term memory for approved facts and commitments that belong to the enterprise, and learnings distilled from validated outcomes and corrections. The article stresses that a transcript is not automatically enterprise memory. Trusted Context sits within Salesforce’s Enterprise AI Harness, alongside Trusted Models, Agency, Actions, Governance and Security, and the same governed context reaches Agentforce, custom and partner agents, and SaaS assistants through SDKs, API adapters, MCP and APIs. The authors also report performance results across production retrieval, high-concurrency queries, analytical SQL, ClickBench, TPC-derived and LDBC graph workloads, while noting these are not directly comparable. They propose an Agentic Context Benchmark, which would count a result only when the resulting action is both authorized and completed. New capabilities are planned to begin rolling out in early FY28, with availability varying by product, region and agreement.

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

Worth reading?