microsoft / microsoft/dynamics365patternspractices
[CATALOG]: [ERROR]: 19 scenarios in the July 2026 catalog have an empty product column although the title names the product
@rachel-profitt is already working on this.
Since Aug 7, 2026.
- Dominant language
- Python
- Stars
- 227
- Forks
- 106
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 1
Description
Contact details
lholck@pingala.eu
Organization type
Partner / ISV / Independant consultant
End-to-end business process
Order to cash
Which business process area is this article related to?
several
Which business process is this article related to?
several
Which pattern or practice is this request related to?
Several
Please describe the suggested change. If this is an update to an existing row in the catalog, please be sure to indicate in the comments.
Catalog version: July 2026
Issue: 19 scenario rows outside the Administer to operate end-to-end process have an
empty product column, although the scenario title explicitly names a product (e.g. "…in
Dynamics 365 Finance", "…with Power BI"). Sibling scenarios under the same level-3 process
with equivalent titles do carry the product value, so these rows look like accidental
omissions rather than intentional blanks.
| # | Process sequence ID | Microsoft ID | Product named in / implied by the title |
|---|---|---|---|
| 1 | 30.05.200.125 | d6689987c36993v0 | Microsoft 365 (title: "…with Microsoft Project") |
| 2 | 30.35.100.225 | d6689987c1734v0 | Sales (title: "…CE apps") |
| 3 | 30.55.500.100 | d6689987c2020v0 | Sales (title: "…CE apps") |
| 4 | 40.10.015.400 | d6689987c2085v0 | Power BI |
| 5 | 40.60.100.100 | d6689987c2585v0 | Power BI |
| 6 | 40.60.100.200 | d6689987c2586v0 | Customer Insights - Data |
| 7 | 40.60.300.500 | d6689987c2622v0 | Customer Insights - Journeys |
| 8 | 40.90.100.300 | d6689987c2672v0 | Customer Insights - Journeys |
| 9 | 40.90.200.400 | d6689987c2691v0 | Customer Insights - Data |
| 10 | 40.90.400.300 | d6689987c2724v0 | Customer Insights - Data |
| 11 | 55.70.045.400 | d6689987c37024v0 | Finance (title: "…in Dynamics 365 Finance") |
| 12 | 55.90.030.400 | d6689987c4106v0 | Power BI |
| 13 | 55.90.050.300 | d6689987c4134v0 | Power BI |
| 14 | 65.30.055.100 | d6689987c37043v0 | Finance (title: "…in Dynamics 365 Finance") |
| 15 | 80.20.200.300 | d6689987c7309v0 | Human Resources (title: "…in Dynamics 365 Human Resources") |
| 16 | 85.15.100.100 | d6689987c49728v0 | Sales (title: "…CE apps"; seven siblings carry Sales) |
| 17 | 85.15.100.200 | d6689987c49729v0 | Sales (title: "…CE apps"; seven siblings carry Sales) |
| 18 | 90.70.065.200 | d6689987c9088v0 | Power BI (title: "Use Power BI for…") |
| 19 | 90.70.065.201 | d6689987c9089v0 | Business Central (title: "…in Dynamics 365 Business Central") |
The suggested product values for rows 1–3 and 16–17 are inferred from the catalog's own
convention for equivalent titles and from sibling scenarios under the same level-3 process;
the rest name the product directly in the title.
Expected: the product column populated consistently with the title, matching sibling rows.
Impact: any consumer filtering the catalog by product (e.g. to exclude products not in a
customer's scope) silently misses these scenarios.Comments go here
Code of Conduct
- I agree to follow this project's Code of Conduct
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.