Latest industry insights, tutorials, best practices and case studies.
1091 articles
Using the 'Query Kingdee Departments' strategy as an example, this guide demonstrates how to use the Qeasy Data Integration Platform to pull ERP department master data into the middleware on a scheduled cadence. We break down source-system metadata modeling, incremental-start design, and common pitfalls, giving engineers in private-deployment environments a reusable configuration blueprint.
This tutorial systematically reviews the Jky erp.storage.goodsdocin.v2 query interface, covering main and detail field mappings, pagination/incremental patterns, and lessons learned from real Jky-to-Kingdee supply chain integration projects.
This article walks through a single strategy — syncing WMS refund/exchange orders from Wangdiantong into MySQL — on the Qeasy data integration platform. It covers incremental time-window pulls from wdt.refund.query and REPLACE INTO writes for both master and detail tables.
This tutorial consolidates multiple real customer projects to systematically unpack the 17 strategies for integrating Kingdee Cloud Sky with DingTalk, focusing on field mapping, code lookups, and exception handling for expense requests, reimbursements, and repayment documents. It distills common practices such as hub-first execution, reserve fund offsetting, and department field splitting so engineers can master this integration domain in one read.
This tutorial uses a retail enterprise's MySQL WMS outbound order database to explain how to query order line items with unmaintained material gross weights and push alerts to DingTalk robots. It covers field mapping, incremental queries, three-table joins, filtering conditions, and how the Qeasy data integration platform wraps this interface — a practical guide for integration engineers.
The Jushuitan after-sales order query (non-Qimen channel) is the core path for syncing after-sales data into SQL Server. This guide aggregates insights from multiple real-world projects into a systematic field mapping, pagination & incremental strategy, status enums, and nested items handling, with lessons learned and stable configurations.
AI 工程最难的不是「做对」，是「错了之后系统怎么继续活着」。D-V7 fire-and-forget 让 API 启动 < 1 秒，把 embedding 回填推到了后台，但后台任务的命运从来不会一帆风顺——DashScope 限流、网络抖动、模型维度变更、单条 content 超长被截断，任何一个都可能让一整批 10 条 chunk 的向量求值失败。本文拆解的是这套系统在「失败兜底」上的 4 个工程决策：失败 chunk **写 1536 维全零向量（不是 NULL）+ 标 `KnowledgeChunkEmbeddingStatus.failed` + 召回 SQL 硬过滤 `kc."embeddingStatus" = 'ready'` 不误命中 + 每批本地 Set 跟踪失败 ID 防死循环 + 下次 bootstrap 自动重试**。这 4 条合在一起构成了 AI 知识库「错了但不死、错了还能修、错了也不会污染召回结果」的最小可用韧性。
大促不是"账单变多"那么简单——是 7 天内涌入平时 30 倍的账单行、3 倍的退单率、5 倍的平台扣点波动。某美妆品牌 2025 年双 11 因准备不足，第 7 天才完成 11 万单的对账，第 15 天才出完月报，错过了 Q4 现金流预测的窗口，被审计师标为"内控薄弱项"。这篇文章不讲促销玩法，给出一份**大促财务核算的作战手册**：3 大准备工作（对账脚本预跑、压测数据、回款预测）+ 5 大对账节点（首日 / 3 日 / 7 日 / 15 日 / 月结），让 CFO 和财务经理把"大促后的财务大崩溃"变成"大促后的财务快报"。
一份抖店资金账单只有 39 列、约 6 千行，却能同时承载货款结算、退款、补贴、佣金、运费险、拦截费、提现七类业务，每类还要落到独立的核算项目。抖店拆分子行就是把一行业务数据按"非零金额列"和"动账场景"双重维度拆成多条带 rowSeq<0 子行的 BillRow，让同一笔订单能在收入对账池和费用对账池里同时被识别为正确的核算项目。
After sales outbound, MES generates a tracking number in MySQL that must be written back to the sales outbound document in Kingdee Cosmos. This article uses one single strategy as a blueprint, covering incremental start point, field mapping, save API invocation and common pitfalls, suitable for supply chain integration teams in private deployment environments.
In the Wandiantong–Kingdee Cloud supply chain integration scenario, managing the validity period of the access token is the prerequisite for stable data push. This article focuses on the single strategy 'Refresh Kingdee Cloud Token', explaining the data flow of authentication refresh, key configuration points on the Qeasy platform, scheduling design, and lessons learned, helping enterprise IT teams avoid data flow interruption caused by token expiration.
This deep-dive tutorial explains, at the single-strategy level, how to periodically query customer master data from Kingdee Cloud Stellar and land it into the Qeasy integration platform's intermediate layer, addressing common issues like mismatched codes and stale organizational data downstream. It covers data flow, field mapping, scheduling strategy, and pitfall reviews.
This guide focuses on the single strategy of synchronizing purchase receipt documents from Wanjtd to Kingdee Cloud Galaxy. It covers data flow, field mapping, Qeasy configuration, phased scheduling, and common risks, helping enterprises build a traceable, retryable, and posting-safe integration flow.
This tutorial drills into one specific strategy (Jike Cloud inventory loss outbound → Yonyou NCC other outbound for non-factory warehouse), covering its business context, field mapping, configuration in Qeasy, incremental plus full-volume dual-track scheduling, and common pitfalls, so enterprise IT teams can apply it directly.
This tutorial aggregates hands-on experience from multiple customer projects to systematically dissect Xiaoman OKKICRM's Product Query interface (API: /v1/product/list), covering field semantics, invocation patterns, and common pitfalls, along with configuration guidance on the Qeasy platform.
Using the CRM-to-ERP customer master sync as a concrete example, this article walks through one strategy from scenario, field mapping, Qeasy platform configuration, to incremental and full-load scheduling, and ends with lessons learned and boundaries.
This article walks through a single strategy—syncing Wangdiantong sales outbound orders as Kingdee Cloud direct transfer documents—covering scenarios, field mapping, Qeasy configuration essentials, phased scheduling, and lessons learned, helping enterprise IT teams land inventory sync in private deployments.
This tutorial walks through a single sales-outbound sync strategy from Jushuitan to Kingdee Cloud Cosmic. Starting from a real retail pain point, it explains data flow, field mapping, Qeasy configuration essentials, and lessons learned on dual-track incremental+full sync, status filtering, and centralized code mapping.
In multi-system integration scenarios, if a sync strategy fails silently, business risk quietly accumulates. This article uses the "DingTalk error push" strategy as an example, walking through how Qeasy periodically pulls error details and pushes anomalies to the ops group via a DingTalk custom robot. It covers field mapping, configuration points, phased scheduling, and lessons learned.
This tutorial focuses on a specific material master data sync strategy: pushing attribute-light materials/products from an ERP system to a WMS. It covers the business scenario, data flow, field mapping, configuration highlights on the Qeasy platform, phased rollout, common pitfalls, and applicability boundaries.
