Semantic Layer on DataAgentX

Data Agent Weekly: Implementation Challenges at DACon26

Sun, 25 Oct 2026 00:00:00 +0000

Covering October 18–24, 2026 (Beijing Time). This issue focuses on six engineering challenges distilled from 19 sessions at the Beijing leg of DACon26, with other developments organized by product and open-source categories.

On October 23–24, DataFun hosted the Beijing leg of DACon26. The six issues below are synthesized from relevant official agenda items; the commentary in this article represents editorial technical analysis. Session titles used here are abbreviated; for full official titles and speakers, refer to the DataFun official agenda link in the Sources section at the end.

The 2W1H of the Semantic Layer for Agents: Why It's Needed, What It Is, and How to Build It

Fri, 23 Oct 2026 00:00:00 +0000

Does connecting to a database and generating SQL guarantee that an Agent will answer business questions correctly?

When asked the same question, “What was last quarter’s revenue?”, different tools yield different answers: a BI tool might include taxes and shipping costs; a Notebook might fail to deduct discounts and returns; finance may recognize revenue based on shipment dates, while the Agent is still guessing how tables relate.

Tencent Cloud DataBuddy: The First Signs of RSI in Data Agents

Tue, 20 Oct 2026 00:00:00 +0000

The Tencent Cloud DataBuddy team announced the new version of DataBuddy during a live stream on the DataFunTalk WeChat video account. The materials do not specify the broadcast date; this article was compiled on October 20, 2026.

Two points are particularly noteworthy: DataBuddy can connect to existing external data sources, not just those on Tencent Cloud; and in the future, models can also integrate proprietary APIs, such as those for Claude and ChatGPT.

Data Agent Weekly: What Are Teams Globally Building?

Sun, 18 Oct 2026 00:00:00 +0000

Covering October 11–17, 2026 (Beijing Time). This week begins with four domestic developments before moving to global progress.

Synthesizing these updates, ten signals point in the same direction: The competition for Data Agents is shifting from “can it answer” to “can it participate in work continuously and reliably.” This manifests as reusable applications, inheritable context, semantics preceding execution, and verification built into workflows.

Domestic: Turning Analysis Paths into Reusable Assets

01 Alibaba Cloud Quick BI: Attribution Logic and Asset Reuse (10/13)

How to Build a Data Agent: A Working Map from 23 Articles

Sun, 04 Oct 2026 00:00:00 +0000

After surveying many Data Agent products, a team beginning implementation still faces five basic questions: What work should the system own? Which data should it use? How may it execute? How will we prove the result? Who remains accountable when it fails?

Those questions are more durable than a vendor list. They connect definition, architecture, autonomy, evaluation, and rollout.

The diagram below maps those questions onto an operating path: how a task enters the system, how semantics constrain planning and execution, and how evidence, approval, read-back, and feedback close the loop.

Inside DataBuddy: Why Data Agents Need a Shared Data Foundation

Tue, 29 Sep 2026 00:00:00 +0000

An analytics agent reports 120,000 new users. The operating dashboard says 108,000. Both can show their SQL, and both claim to use current data. The problem is larger than one wrong answer: do the agent and the existing data products share the same assets, semantics, identity, and controls?

That question makes DataBuddy’s architecture more interesting than its three visible roles—data engineering, analytics, and governance agents. Underneath them, the product connects ingestion, lakehouse storage, catalog, unified semantics, and AI-ready data knowledge into a shared chain. An Agent Harness ties that chain to context, tools, security, and evaluation.

How a Data Agent Understands Average Order Value

Mon, 28 Sep 2026 00:00:00 +0000

“What is average order value by category over the last 30 days?” A model can easily produce valid SQL and an invalid business answer. Average order value may be paid amount divided by paid orders, exclude refunds, use buyers as the denominator, or count only fulfilled orders.

This is not primarily a SQL problem. The phrase has not yet been bound to executable meaning.

Google Cloud Data Agents Converge Three Kinds of Context

Tue, 22 Sep 2026 00:00:00 +0000

Knowing where a table lives is not the same as knowing how to answer a business question. Google Cloud describes Conversational Analytics data agents as a combination of context and tools: business information and data provide context; SQL, Python, and visualization tools perform work.

Three contexts have different authority

Data context identifies queryable objects, fields, relationships, and locations. Business context explains terms, metrics, filters, and verified queries. Conversation context retains the user’s scope, assumptions, and follow-up questions across turns.

OpenAI Data Agent Connects Enterprise Data, Dashboards, and Action

Fri, 11 Sep 2026 00:00:00 +0000

On September 10, 2026, OpenAI launched Data Agent in ChatGPT Work. The release is more than a Text-to-SQL chat interface: it connects enterprise sources, business context, analytical workflows, interactive dashboards, and approved actions in one conversational path.

The competitive question shifts from whether a model can write a query to whether more employees can complete reviewable data work under existing organizational controls.

Why Stronger Data Agents Need a Semantic Layer

Tue, 08 Sep 2026 00:00:00 +0000

Give a model the schemas for orders, payments, and customers and it can quickly produce executable SQL. Ask “What was revenue last month?” and the real work begins. Does revenue mean booked value, cash received, net receipts, or recognized revenue? Which date applies? In which period do refunds belong?

Those are not universal facts for a model to infer. They are enterprise contracts. As an agent gains tools and a longer execution chain, the cost of propagating one incorrect definition into a report or action increases.

A Seven-Layer Architecture for Production Data Agents

Mon, 07 Sep 2026 00:00:00 +0000

“Why did new-customer conversion fall this month?” sounds like a SQL question. It is not.

Before touching a warehouse, a useful Data Agent has to establish what new customer means, which conversion window applies, whether the metric changed recently, which data the requester is allowed to see, and what evidence would make an explanation credible. A query can run perfectly and still answer the wrong question.

Production Data Agents therefore need more than a language model and a database connector. They need a chain of responsibilities that turns ambiguous intent into a result another person can inspect. The seven-layer model below is a way to design that chain—and, when it breaks, to locate the failure.

Five Data Agent Routes: Compare Products by the Work They Own

Sat, 05 Sep 2026 00:00:00 +0000

One Data Agent turns a business question into SQL. Another runs queries and Python, then writes a report. A third edits a production pipeline. They share a category name, but they should not share one scorecard.

The useful unit of classification is a workflow, not a vendor. Ask four questions: What enters the system? Which part of the work does it own? What does it deliver? What is the blast radius when it fails? Those questions reveal five recurring routes.

The SQL Ran. Why Is the Answer Still Wrong?

Fri, 04 Sep 2026 00:00:00 +0000

The most dangerous result in analytics is often not a failed query. It is a query that runs cleanly, returns a precise number, produces a polished chart—and answers the wrong question.

Suppose an operator asks, “How many new customers did we acquire this month?” The system finds a customer table, counts distinct IDs by created_at, and returns 12,486. The query is reproducible and syntactically correct. But Sales defines a new customer as a first-time payer, while Finance excludes refunded transactions and internal test accounts. The query counted new customer records, not the metric that will drive the budget decision.

What Is a Data Agent? Four Practical Tests

Thu, 03 Sep 2026 00:00:00 +0000

“Why did conversion fall this week?”

An NL2SQL tool can translate that sentence into a query. A data agent has a larger job. It must establish which product and funnel the question refers to, decide whether “this week” means a calendar week or a rolling seven-day window, and respect what the current user is allowed to see. It then has to find trusted data, apply the right metric definition, investigate the change, run and check its queries, and return evidence with the conclusion.