microsoft / microsoft/BCApps

[Document Reporting]: Migrate existing Word report layouts to the new composite document report structure [Vendor Work]

Open
#9,655 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

  • #10240 by @MSlenejennum — closed without merging
BCIdea Team: Integrations
Dominant language
AL
Stars
683
Forks
459
Avg merge
3d 26m
Merged PRs (30d)
633

Description

BC Idea Link

https://dynamicssmb2.visualstudio.com/Dynamics%20SMB/_workitems/edit/643211

Description

Business Central is moving to a new composite document report structure, where a report's header, body, and footer are separate, reusable layouts instead of one monolithic Word layout. To fit this structure, every existing report that currently has a Word layout needs a dedicated body layout that works standalone and supports theming.
Goal: Deliver a body layout for every existing report that already has a Word layout, so they all fit the new composite structure.
Work per layout:
Consolidate similar layouts: where several layouts in the old structure are near-identical, merge them into a single shared body layout instead.
Remove header/footer so only the body remains
Make sure to set up the proper header & Footer design default for the end user per report
Ensure the body layout elements render correctly when a theme is applied
Smoke test that the final body layout works in the composite world (Human Test)
Compare the output of the old layout against the new layout (ideally automated).

I will provide the implementation for this BC Idea
  • I will provide the implementation for this BC Idea

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.

Research direction

Start by locating the existing Word layouts for Business Central reports and read the composite document report structure guidance linked from the BC Idea. For each applicable report, create or consolidate a standalone body layout, remove header and footer content, verify theme rendering and header/footer defaults, then smoke-test and compare the old and new output.

Written by the indexing model from the issue text.

Assessment

Domain
design
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.