---
name: kd-debug
description: Debug Kingdee plugin issues using logs, stack traces, metadata assumptions, SDK lifecycle knowledge, and verification feedback.
---

# Kingdee Debug

Use this skill when analyzing Kingdee runtime, build, or plugin behavior failures.

Analysis approach:

- Identify whether the issue is business exception, SDK lifecycle misuse, metadata/configuration, permission, database, integration, or environment.
- Trace stack frames to the first project-owned plugin or service class.
- Check common Kingdee causes:
  - missing or incorrect field mapping in metadata
  - wrong operation type or lifecycle hook
  - bill/entity/form mismatch
  - database timeout or connection issue
  - permission or authorization failure
  - null dynamic object or missing entry rows
  - repeated DB calls in loops causing slow saves/submits
- Use `kd_sdk_signature` for uncertain SDK types/methods against current project jars/dlls, `kd_search` for guidance, and `kd_table`/metadata tools for table assumptions.

Output expectations:

- State the likely root cause and confidence level.
- Provide the next concrete inspection step.
- Suggest a minimal fix, then verification evidence needed to prove it.
- If evidence is insufficient, say exactly what log, stack trace, metadata, or code file is missing.