microsoft / microsoft/dynamics365patternspractices

[ERROR]: Import of Sbd Delivery Plan JUL 2026 fails

Open
#357 0 comments 0 reactions 1 assignee View on GitHub

@rachel-profitt is already working on this.

Since Jul 28, 2026.

bug
Dominant language
Python
Stars
227
Forks
106
Avg merge
2d 13h
Merged PRs (30d)
1

Description

Contact Details

glev@syntoralis.eu

Describe the error you see in the documentation, or the correction you suggest

Problem

During Phase 5 (catalog import) of the SbD Delivery Plan JUL 2026, 1 item fail "with Missing target work item type: Not Found"

Root Cause

Line 557 is empty in the SbD Delivery Plan JUL 2026

  • Are not properly normalized during the import process

Impact

  • Import failures block completion of Phase 5
  • Catalog items with invalid or missing values cannot be imported
  • Users must manually remediate by deleting the line.
  • Setup process is delayed and requires troubleshooting

Expected Behavior

The import should either:

  1. Ignore empty line OR
  2. Provide clear validation guidance before import begins to identify empty lines.

Steps to Reproduce

  1. Run full setup wizard with business process catalog
  2. Observe Phase 5 import failures
  3. Check import-failures.json output file for :
    "Missing target work item type: Not Found"

Remark : Time consuming first error stop the import.

Environment

  • Setup tool: July release (setup_wizard.py)
  • Phase: 5 (Catalog Import)
  • Output artifact: import-failures.json

Suggested Solutions

  • Add pre-import validation to detect empty line before attempting import
  • Include remediation guidance in import failure reports
Link to the article where the error is

--

Code of Conduct
  • I agree to follow this project's Code of Conduct

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.