[ERROR]: BPCTool skips Process type and Organizational scope type fields ("missing picklist") on first run #372

Contact Details

simon.lamb@velrada.com

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

Summary
On a fresh install (new process and new project) with ADO template guidelines - OCT 2026.xlsx, BPCTool's process step creates the two new picklists (Process type, Organizational scope type) successfully, but then skips both fields:

Skipping field 'Process type' — missing picklist
Skipping field 'Organizational scope type' — missing picklist

No Picklist '…' warning is logged. Afterwards both picklists exist in the org (GET _apis/work/processes/lists), while MSBPC.processtype and MSBPC.organizationalscopetype return 404. Layout then fails with TF51535: Cannot find field … for these controls on Configuration, Deliverable, Documentation, Integration, Job, Migration, Workflow (Organizational scope type) and Process, Scenario, System process (Process type).

Likely cause
BPCTool/bpctool/runner/app/writers/process.py creates new picklists via POST, then immediately re-reads GET /_apis/work/processes/lists (around line 209) and looks each list up by name. The freshly created lists aren't in that response yet (ADO read lag), so picklist_ids.get(label) returns None and the field is skipped.

The org already contained the MSBPC.* fields and picklists from an earlier, separate setup, so only these two October-only picklists took the POST path. On an empty org every picklist would be new, so all picklist fields are likely affected.

Suggested fix
Use the id returned by the POST/PUT response instead of re-reading the list, or retry the lookup briefly before skipping.

Workaround
Re-run the process and layout steps. The picklists now exist, so the fields are created.

Minor, related
Every existing MSBPC.* field logs Field '…' warning: ADO 404 Not Found from the PATCH /_apis/wit/fields/{ref} call. Harmless, but it pushes real warnings out of the UI's 120-line log view.

Environment
BPCTool at commit b664b28, Azure DevOps Services.

Link to the article where the error is

https://github.com/microsoft/dynamics365patternspractices/tree/main/templates/Azure-DevOps-templates/BPCTool

Code of Conduct

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