Latest industry insights, tutorials, best practices and case studies.
571 articles
This article takes subcontracting purchase inbound sync as the entry point, detailing the single-strategy configuration from Kingdee YXC V2 to WangdianTong QiM. It covers field mapping, incremental scheduling, subcontracting warehouse identification, and lessons learned to help enterprise IT teams quickly achieve data flow for subcontracting inbound business.
This article uses the 'Query DingTalk Employee' strategy as a sample to break down the source-side configuration for pulling employee profiles from DingTalk, the intermediate landing point as a no-op write, and the scheduling and dependency design on the Qeasy Data Integration Platform, providing reusable implementation steps and pitfall lessons.
This tutorial aggregates field-tested experience from multiple customer projects, systematically explaining the order sync interface between Xiaoman OKKI CRM and Digiwin T100, covering field mapping, incremental strategy, code alignment, and exception handling across customer, product, and order documents, with practical configuration guidance on the Qeasy platform.
This guide covers reverse-syncing Guanyi expense flows into Kingdee Cloud payment refund vouchers on a monthly basis. It walks through API configuration, field mapping, scheduling strategy, and lessons learned, helping teams complete historical finance archiving in a public cloud deployment.
This tutorial walks enterprise IT teams through configuring the Qeasy Data Integration Platform to convert inventory surplus documents from Kingdee Cosmic into miscellaneous inbound orders in Wangdiantong. It covers use-case value, field mapping, configuration essentials, phased scheduling, and common pitfalls.
This tutorial focuses on a real-time inventory stock-take sync strategy between Kingdee Cloud Galaxy and Jushuitan. It covers the business scenario, field mapping, Qeasy platform configuration, phased scheduling, and lessons learned, helping enterprise IT teams quickly close the inventory reconciliation loop.
Focused on supply-chain integration, this guide shows how to use a single strategy to write a WDT order number back into a Kingdee Cloud transfer-in document's remark or custom field. It covers data flow, field mapping, Qeasy configuration essentials, scheduling, and common pitfalls.
This article focuses on a single strategy: 'Periodic Cleanup of Data Older Than 90 Days'. It explains how to use the DeleteStrategyData API together with a no-op write strategy on the Qeasy Data Integration Platform to periodically purge historical documents such as sales outbound orders from Kingdee Cosmos, reducing storage pressure and avoiding performance and compliance risks caused by data bloat.
This tutorial walks through a single strategy: incrementally syncing the Kingdee Cloud bill of materials (ENG_BOM) into a MySQL BOM entry master table, covering data flow, field mapping, key configuration points in Qeasy, scheduling, and practical pitfalls for supply chain master data integration.
For retail scenarios, this guide explains an one-to-one write pattern that incrementally syncs Jushuitan sale-out orders into Chanjet T+ sale delivery vouchers. It covers source filtering, field mapping, _findCollection cross-strategy lookup, ExternalCode concatenation, non-merging write mode, phased scheduling and pitfalls.
The Custom Data Processing Factory is a programmable extension capability provided by the Qeasy Data Integration Platform (DataHub) at key points in the data flow lifecycle. It covers five lifecycle hooks—from source ingestion to target push—allowing users to rewrite, supplement, or split data through PHP code. It addresses complex business requirements such as field recalculation, entry appending, and reverse auditing, thereby enhancing integration flexibility and controllability.
Material category is the first button of supply chain integration. If the code mapping is wrong, every downstream sync gets distorted. This article uses the material category sync strategy from Kingdee Cloud to Midea Cloud as an example, explaining the data flow, field mapping, key configuration points in Qeasy, phased scheduling, and lessons from real-world pitfalls.
This tutorial focuses on the other-outbound-stock strategy syncing from Jushuitan to Kingdee Cosmic Star. Built around Qeasy (the data integration platform), it walks through field mapping, incremental starting point, scheduling cadence, and real-world pitfalls, giving integration engineers a practical, strategy-level playbook.
This article focuses on the sales order header status refresh strategy, explaining how to align status fields between MySQL on the MES side and Kingdee Cloud on the ERP side. From scenarios and field mapping to Qeasy configuration, implementation steps, and lessons learned, it offers a practical tutorial for supply chain integration in private deployments.
This article walks through the supplier master status writeback scenario: pulling approval status from Kingdee Cloud and writing it back to a MySQL business table. Drawing on a private-deployment retail project, it covers field mapping, scheduling, and typical pitfalls on the Qeasy data integration platform.
把过去 18 个月里新用户和开发者最容易复发的 10 个错误拆成 3 大类——数据规范类（4 个，金额符号、双零判定、CONFIRMED 闸、暂估/财务应收并存）、沙箱与脚本类（3 个，不试跑直接保存、OTHER 误用、聚合范式漏注册）、AI Agent 与工程类（3 个，Agent 缺 SKILL、跨店跨平台绑定、v3 重构前残留字段）。每个坑都给出「症状 + 根因 + 防御」三段式，至少 7 个坑附真实数字或版本出处，看完能避开 90% 的重复踩雷。
把多平台对账结果送进 ERP，是电商财务系统集成最难的「最后一公里」。文章用一个生产级集成中心的真实工程数据，讲清三件事：① 为什么「拉 ERP 数据 + 下推财务单据」必须被设计成 PULL 与 PUSH 两个方向互不耦合的引擎，而不是一个开关；② 为什么中间必须隔一层「集成转换」——第四类沙箱脚本——把对账结果变成目标系统能懂的单据结构；③ 这三大引擎在 `integration_handlers` 表里如何被统一注册、按 docType 路由、状态机推进。读完之后你会看到，集成中心的复杂度不在于「能不能对接金蝶」，而在于「目标系统换了、字段变了、规则改了，能不能不改代码就接住」。
如果你是电商财务的业务人员，过去一个新平台的解析 / 对账 / 费用分摊脚本要排队等实施工程师 5-7 个工作日；现在用 AI 财务智能体，1 小时就能自助完成。本文不讲技术原理，只讲「5 步工作流 + 6 个反直觉发现 + 4 套提示词模板」——业务人员拿来就能用。如果你已经按 9.1.4 走完「首份收入对账」、按 9.1.5 看完了「首份报表」，本文会把你从「看报表的人」升级为「改脚本的人」。
解析写回后 `incomeAmount = 0` 且 `feeAmount = 0` 的行——也就是账单里的「提现 0 元」「账户内部划转 0 元」「营销两列相抵 0 元」这类行——统一由解析执行层判 `parseStatus = FAILED`，`abnormalReason = "解析后无收入/费用金额"`，不设例外。这条全局规则在 2026-08-06 定稿，覆盖京东 POP / 抖店 / 支付宝 / 亚马逊 / 微信小店 / 速卖通 / 拼多多 / 小红书 / 独立站 9 大平台，是脚本归类结果的「完整性校验」闸——零额 PARSED 残留行会被这条闸直接打成 FAILED，不进任何对账池、不产生"待对账"幽灵记录。实测：亚马逊美站 6 月 42 行双零（订单付款 41 + 订单逆向收费 1）+ 8 行「已推迟」清算（20.22 USD）由 settlement 脚本兜底判 FAILED；支付宝余利宝「转入 / 转出」行的双零行同样命中此规则。
This tutorial dives into a single finance-sync strategy: pushing approved Kingdee Cosmic receipt bills incrementally into a business system, expanding detail lines into bank collection records. It covers data flow, field mapping, Qeasy configuration essentials, phased scheduling, and lessons learned from real projects.
