Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[ERROR]: SbD Delivery Plan JUL 2026: the Workshop assumptions column is exported with the header "Not Found" - 122 workshops silently lose their assumptions on import

Open
  • Is something wrong?
#367 0 comments 0 reactions 1 assignee View on GitHub

@rachel-profitt is already working on this.

Since Aug 10, 2026.

Assessment

This issue has not been assessed yet.

Description

bug
Contact Details

[email protected]

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

Describe the error

In SbD Delivery Plan JUL 2026.xlsx, column 22 (between "Key questions MS BPC" and "Responsible party MS BPC") has the literal header "Not Found" instead of its field name. The column is not empty: it contains workshop assumptions / prerequisites text on 122 rows — all of them Workshop work items (of 135 workshops in the file), e.g.:

"* The acquire to dispose end-to-end business process is in scope for the Dynamics 365 project. * The acquire to dispose scenario board is available and leveraged to conduct the workshop. * The key stakeholders are available and actively contribute to the workshop. ..."

This is clearly the data for MSBPC.workshopassumptions (the ADO template guideline lists Workshop assumptions MS BPC, HTML, data status "Data included").

Because the header is "Not Found", the import tooling cannot map the column to any field and silently drops all 122 values — after a standard import, 122 of 135 workshops have an empty Workshop assumptions field even though the content exists in the source file.

It looks like the same export defect family as the "Not found" area path values (#353) and the "Not Found" work item type row (#357): a lookup in the export pipeline failing and writing its fallback string, here into a column header.

Steps to reproduce
Open SbD Delivery Plan JUL 2026.xlsx, Sheet1.
Look at the header row, column 22: it reads "Not Found".
Filter the column on non-empty values: 122 rows, all Work item type = Workshop, all containing assumptions/prerequisites text.
Import the file with the standard tooling and inspect any of these workshops in Azure DevOps: Workshop assumptions is empty.
Expected behavior

The column header should be "Workshop assumptions MS BPC" (matching the other columns' naming convention), so the import maps the content to MSBPC.workshopassumptions.

Workaround we verified: renaming the header cell to "Workshop assumptions MS BPC" makes the import map the field correctly, and the 122 values import cleanly.

Additional context

Found while verifying a full review of the delivery plan against the source file. A pre-import validation that flags sentinel headers ("Not Found") on non-empty columns would catch this class of error before data is lost.

Link to the article where the error is

bpc

Code of Conduct
  • I agree to follow this project's Code of Conduct
Dominant language
Python
Stars
234
Forks
108
No merged PRs in 30d

Getting set up

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.

More from microsoft/dynamics365patternspractices

All issues in microsoft/dynamics365patternspractices

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.