The example reconciles two eligible Task IDs and one expected To-do omission. Draft's Check is ta01; Review's Check is tb02; Email venue is To-do td03. The supplied tb02 dependency points to ta01 with FS type. The helper checks an illustrative export-ID list against those logical identities and holds a merged-label or missing-task case. It does not convert a map or produce a workbook.
Identify the export mode first
XMind's current Task export guide documents Excel(Task) as CSV, not proof of an .xlsx workbook or tested online converter. Confirm actual version, feature availability, account access and export mode before following native steps. Ordinary Excel export and legacy layout modes are different contracts. After exporting, record the actual headers, selected scope, summary rows, and native Task IDs. Keep those observations tied to the version and export mode that produced them.
The original Workshop map has summary branches Draft and Review. ta01 and tb02 are separate Task-created topics labeled Check under those branches. td03 is a To-do labeled Email venue. These are authored aliases, not captured native Topic IDs. Record the real IDs and map them to the aliases after native preparation. Expected detail-task eligibility is exactly ta01/tb02; td03's absence is expected scope exclusion, not evidence of completion, deletion or data loss.
Keep duplicate labels distinct
Joining by Check would collapse two topics and erase their branch contexts. Use the actual Topic/Task ID for identity and task path as context. The guide links Task ID to Topic ID and describes paths through ancestor summary tasks. A path string or display name is not a replacement for the actual identifier. Check that both eligible detail records are present, while leaving total physical CSV row count open because headers or summary entries depend on the real output being inspected.
The local helper accepts a comma-separated logical-ID set and separately checks the dependency field. ta01,tb02 is complete for this fixture; ta01 alone holds missing tb02. Adding td03 invents a Task record outside the declared eligible set and fails the comparison. Duplicate IDs also hold. These cases make the intended scope explicit before inspecting an actual spreadsheet, without pretending that manually entered aliases came directly from an XMind export or that two rows alone prove the correct identities survived.
Preserve target identity and dependency type
The authored relationship is tb02 depends on ta01 with FS type. Illustrative notation ta01FS represents target alias plus type; replace it with the native target Topic ID/type from evidence, not the label Check. Keep the raw dependency field before interpretation. Its internal comma-separated entries belong inside CSV field structure, not as additional CSV rows. An unknown target, changed type or merged-name target requires investigation rather than a successful-looking dependency cell.
Finish with coverage and spreadsheet interpretation as separate checks. Retain map revision, export mode, actual native ID mapping, raw headers/fields and observed import behavior. Inspect delimiter handling, identifiers, task paths and dependency types after Excel reads the CSV. A successful native export alone does not establish a correct spreadsheet interpretation. Preserve expected To-do exclusion alongside actual coverage, and rerun the affected reconciliation when map types, scope or revisions change before calling the conversion complete.
Make your own working example
Build an original XMind Task-export reconciliation aid, not a converter. Source Workshop has Draft/Check Task alias ta01; Review/Check Task alias tb02; Review/Email venue To-do alias td03. Aliases are illustrative, not actual native Topic IDs. Expected eligible detail IDs ta01,tb02; td03 is intentionally outside Task export scope.
Provide comma-separated exported-alias input default ta01,tb02 and dependency field default ta01FS for tb02. Reconcile checks exact distinct IDs, missing eligible records, unknown/excluded additions and duplicate IDs. Preserve the two Check labels as distinct source rows with paths. A Merged Check case loads only ta01 and holds missing tb02. A Wrong dependency case changes target to unknownFS and holds the relation. Reset restores valid sample records.
Keep source inventory, eligible IDs and dependency target/type visible. Explain actual Task ID equals native Topic ID, and current Excel(Task) is documented CSV. Native version/online access/headers/summary-row count and Excel import remain untested. Do not fabricate td03, merge by name, parse internal dependency commas as extra records, create a fake workbook download or imply completion of a real conversion.
Use one self-contained HTML file with no remote dependency. Keep the initial sample, output, and labeled controls near the top. Use at least 16px text, strong contrast, visible focus, and a stacked layout at 360px without horizontal overflow. Use explicit type=button click handlers and explicit DOM selectors; do not depend on native form submission. Clear stale feedback when task inputs change. Render entered text safely. Keep practice data local to the current page; do not imply saving, sending, or production integration. Return only the finished HTML.
Clarify the expected omission
Keep the native map, CSV and actual ID mapping together. For an HTML reconciliation brief, NOS lets you revise eligible static notes visually without AI regeneration. Clarify that Email venue is a To-do before someone treats its Task-export omission as lost work.