Today4 stories · 3 briefs

The Daily Org

Spring '27Sandboxes 6 Feb 2027

Curated by Abhinav (opens in a new tab)

Vol. I · No. 44The independent daily for Salesforce admins, developers and architects4 stories · 3 briefs

Must-readIntegration

Building a Salesforce–NetSuite sync in Python that proves the two systems agree (opens in a new tab)

You will see how to enforce field ownership in code, make Salesforce and NetSuite writes retry-safe with external ID upserts, stay inside NetSuite's concurrency limit, and run a reconciliation report that catches drift.

Why read this

The worked code is Python with httpx and psycopg, not Apex.

  1. Source record changes and is enqueued
  2. Worker claims due rows under a lease
  3. Upsert by external ID to the other system
  4. Success marks the version as sent
  5. Retryable error backs off and retries
  6. Ambiguous match parks for review
Each change moves through the queue, from enqueue to upsert, with retry or review on failure

A software services client ran an off-the-shelf Salesforce–NetSuite connector for years, and the data drifted: customer names, invoice statuses and billing contacts stopped agreeing, and a sales rep’s edit once overwrote a legal billing name in NetSuite. The author argues that most CRM-to-ERP integrations fail by drifting rather than crashing, and rebuilds the integration around explicit field ownership, external IDs and a reconciliation report.

Field ownership is kept as data. NetSuite owned legal entity, billing terms, invoice balances and payment status, while Salesforce owned segmentation, Opportunities and account-manager assignments. Each outbound payload is built only from fields the source system owns, and mirrored fields are read-only in Salesforce. Records are matched through external IDs on both sides, and a cross-reference table holds the linkage, with a needs_review status for ambiguous matches.

Writes go through a queue holding one desired state per record with a version number, so repeated edits produce a single write. Workers claim rows with a lease, and writes are upserts by external ID, so a retry after a timeout does not create duplicates. The code shows how NetSuite and Salesforce each respond to upserts and to errors such as 429 and 300. Concurrency is capped with semaphores because NetSuite limits concurrent requests per account across all connectors. Invoice changes are pulled with SuiteQL using a keyset checkpoint, and a nightly reconciliation classifies each invoice as matched, stale, missing or wrongly linked.

The parallel run of the new integration against the old one exposed overwrites, wrong bill-to links and missed status updates. Invoice status went from a lag of 24 to 48 hours to normally 10 to 15 minutes, and the finance spreadsheet was retired once the daily report explained every remaining difference.

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

Worth reading?

RecommendedAgentforce and AI

Exposing HXL widgets to Slackbot through a custom MCP server (opens in a new tab)

You will learn what a custom MCP server needs before Slackbot can render HXL widgets, how to connect Slack through the Salesforce Org Connection, and how to set tool permissions and descriptions so the right tool is chosen.

Why read this

You will also see how to troubleshoot a missing card.

  1. Check the MCP server definition
  2. Map users by Federation ID
  3. Request and approve the org connection
  4. Add the MCP server in Slack admin
  5. Turn on the server and set tool permissions
Steps to make an HXL widget appear in Slackbot, in the order the article gives them

The article explains how to make an existing HXL widget appear in Slackbot. If a widget already renders in Claude or ChatGPT, it can render in Slackbot without changes to the widget, the Apex action or the Custom Lightning Types. The remaining work is configuration: deciding how Slack connects to the Salesforce MCP server, who can use it, and which tools Slackbot may run. The author uses the Pronto sample app to show a storefront card and a follow-up menu card.

Before connecting, the server must be active, every resource needs a description, each tool’s uiResource must match a resourceName, and each tool’s readOnly and destructive flags must be set. Slackbot treats unclassified tools as write tools, which adds confirmation prompts. The connection itself is made through the Salesforce Org Connection: users are mapped by Federation ID, the org is requested and approved from Slack and Setup, and the MCP server is added in Slack admin and confirmed by a Date added value.

Each user then turns on the server in Slackbot and approves tools, choosing Allow once, Always allow or Deny per tool. Two limits apply: up to five active servers per user, and a 60-second timeout per call, with stateless calls that rerun the Apex action, so calls should stay small. Overlapping tools on other servers or Slackbot’s own Salesforce search can cause a plain table instead of the card, so descriptions should be specific.

The troubleshooting section maps common symptoms, such as plain text, missing tools, or blank values, to causes and fixes. Testing with a debugging tool like MCP Inspector helps separate server definition problems from Slack problems.

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

Also told by InfallibleTechie (opens in a new tab)

Worth reading?

Agentforce and AI

Salesforce in Microsoft Copilot and Teams, with zero-copy access to Fabric (opens in a new tab)

You will learn what the Salesforce and Microsoft integrations now offer: Salesforce context inside Copilot and Teams, and bidirectional zero-copy data sharing between Data 360 and Fabric.

Why read this

You will also see which parts are in beta, pilot or generally available.

Data Federation

  • Query Fabric OneLake data in Data 360
  • Source data stays in Fabric
  • Generally available

Data Sharing

  • Share curated Data 360 context to OneLake
  • Supports custom analytics and AI workloads
  • Public preview, beta
Data Federation lets Salesforce query Fabric data in place, while Data Sharing sends Data 360 context to OneLake

Salesforce and Microsoft have announced Copilotforce, a partnership that brings Salesforce customer context and sales workflows into Microsoft Copilot, adds real-time CRM collaboration in Microsoft Teams, and connects Salesforce Data 360 with Microsoft Fabric. Accenture is the design and implementation partner and is deploying the integrations in its own global sales organization.

Salesforce in Microsoft Copilot lets sellers ask natural-language questions and get grounded outputs, prepare for meetings, analyze opportunities and take supported CRM actions. Copilot’s Work IQ layer combines Salesforce data with Teams meetings, Outlook emails and shared documents on SharePoint and OneDrive. The article names three daily workflows: meeting preparation, deal-health analysis and pipeline review with close plans in Word and PowerPoint.

The Sales Cloud in Teams app, which was shown at Dreamforce, is in pilot. It shows pipeline and quota progress, sends deal notifications, and lets sellers update supported opportunity details through adaptive cards, with changes saved back to Salesforce. Agentforce Coworker handles actions within Teams.

On the data side, Data Federation is generally available and lets joint customers query Microsoft Fabric OneLake data inside Data 360 without moving it. Data Sharing is in public preview and beta and lets organizations share curated Data 360 context into OneLake. Access follows existing Salesforce permissions and Sharing Rules, and supported writeback actions require explicit user confirmation and respect Validation Rules. The article stresses that pricing and availability depend on customer agreements.

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

Worth reading?

Architecture

Optimizely compromise injected malicious scripts into Salesforce sites (opens in a new tab)

You will learn how a third-party script vendor was used to inject malicious JavaScript into 178 sites, including several Salesforce domains, and what to audit on your own Salesforce-powered sites in response.

  1. Attackers add code to Project JavaScript field
  2. Optimizely CDN passes code to site visitors
  3. Visitors' browsers run the injected script
  4. Script swaps crypto addresses, takes card data
How malicious code reached visitors through Optimizely's delivery network

Malicious JavaScript was injected into Optimizely’s Web experimentation platform and served to visitors of 178 organizations on November 16, including Salesforce. The code was designed to swap cryptocurrency addresses for the attacker’s own, collect payment card information, and target iOS devices with additional exploit chains. Salesforce says its own systems were not compromised, but it disabled Optimizely scripts across preview and production instances as a precaution while it investigates.

The attackers reportedly placed code in a “Project JavaScript” field in customer Optimizely accounts, which the vendor’s content delivery network then passed on to visitors. It is not yet clear how the attackers gained write access to those accounts. Optimizely has said it fixed the vulnerability, removed the injected code from affected projects, and added security measures. Equifax has stopped using Optimizely altogether.

The affected Salesforce domains named in the research were evergage.com, exacttarget.com, pardot.com and salesforce-scrt.com, along with four others not named. The article treats the incident as a lesson in supply chain risk: a secure platform can still be brought down by a vendor script running on its pages. It suggests auditing the third-party scripts on Experience Cloud and Commerce Cloud storefronts, removing any that are no longer used, and investigating any that nobody in the organization can account for.

For end users, the article recommends updating iOS devices to 18.7.3 or later, or to iOS 26.3 or later, depending on what the device supports.

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

Worth reading?

In brief