[ERROR]: Import of July Business Process Catalogue fails because of "Not found" AreaPath - setup_wizard.py

Contact Details

julija.ludviga@elca.ch

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

Problem

During Phase 5 (catalog import) of the July business process catalog setup, many catalog items fail to import with AreaPath validation errors showing "Not found" in the import failure logs.

Root Cause

Multiple lines in the business process catalog source data reference AreaPath 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 3 (Teams & Areas setup)

Impact

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

Expected Behavior

The import should either:

1. Successfully map AreaPath values from the source catalog to existing project areas, OR
2. Provide clear validation guidance before import begins to identify missing area paths

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 AreaPath "Not found" errors
4. Count occurrences—multiple lines affected

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 AreaPath values before attempting import
• Provide documentation mapping catalog area paths to required Azure DevOps area configuration
• Include remediation guidance in import failure reports
• Consider fallback or default area path handling for unmapped valuesrong in the content!

Link to the article where the error is

--

Code of Conduct

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