microsoft / microsoft/dynamics365patternspractices

[ERROR]: Import of Deliverables JUL 2026 fails

Open
#356 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 Deliverables JUL 2026, items fail to import with :

The field 'Job purpose MS BPC' contains the value 'Recurring batch' that is not in the list of supported values.
The field 'Job purpose MS BPC' contains the value 'Batch (one-time)' that is not in the list of supported values.
The field 'Job type MS BPC' contains the value 'Scheduled' that is not in the list of supported values.
The field 'Job execution type MS BPC' contains the value 'Monthly' that is not in the list of supported values.
The field 'Job execution type MS BPC' contains the value 'Daily' that is not in the list of supported values.
TF401320: Rule Error for field Data type MS BPC. Error code: Required, HasValues, LimitedToValues, AllowsOldValue, InvalidEmpty.

Root Cause

Multiple lines in the Deliverables JUL 2026 source data reference Job purpose, Job type, Job execution type values that either:

  • Do not exist in the target Azure DevOps project
  • Are not properly normalized during the import process
  • Reference area paths that were not created during Phase 1

And missing value for the mandatory field "Data Type" for Migration Work Item Type.

Impact

  • Import failures block completion of Phase 5
  • Catalog items with invalid or missing values cannot be imported
  • Users must manually remediate Job purpose or modify source data to proceed
  • Setup process is delayed and requires troubleshooting

Expected Behavior

The import should either:

  1. Successfully map Job purpose, Job type, Job execution type values from the source catalog to existing project areas, OR
  2. Provide clear validation guidance before import begins to identify missing Job purpose, Job type, Job execution type

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 :
    The field 'Job purpose MS BPC' contains the value 'Recurring batch' that is not in the list of supported values.
    The field 'Job purpose MS BPC' contains the value 'Batch (one-time)' that is not in the list of supported values.
    The field 'Job type MS BPC' contains the value 'Scheduled' that is not in the list of supported values.
    The field 'Job execution type MS BPC' contains the value 'Monthly' that is not in the list of supported values.
    The field 'Job execution type MS BPC' contains the value 'Daily' that is not in the list of supported values.
    TF401320: Rule Error for field Data type MS BPC. Error code: Required, HasValues, LimitedToValues, AllowsOldValue, InvalidEmpty.

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 missing Job purpose, Job type, Job execution type, Data type values before attempting import
  • Provide documentation mapping catalog Job purpose, Job type, Job execution type, Data type to required Azure DevOps area configuration
  • Include remediation guidance in import failure reports
  • Consider fallback or default Job purpose, Job type, Job execution type, Data type handling for unmapped values wrong in the content!
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.