Skip to content

WorkCenter/MachineCenter: add Capacity Shown In to Calendar and Load pages#9214

Open
Busslar wants to merge 4 commits into
microsoft:mainfrom
Busslar:w/busslar/feature-9205-capacity-shown-in-workcenter-machinecenter
Open

WorkCenter/MachineCenter: add Capacity Shown In to Calendar and Load pages#9214
Busslar wants to merge 4 commits into
microsoft:mainfrom
Busslar:w/busslar/feature-9205-capacity-shown-in-workcenter-machinecenter

Conversation

@Busslar

@Busslar Busslar commented Jul 8, 2026

Copy link
Copy Markdown

With reference to microsoft/BusinessCentralApps#1893
Fixes #9205
Fixes #9205

Work Center and Machine Center Calendar and Load pages were missing the Capacity Shown In field that the Work Center Group pages already have. This meant capacity figures were always displayed in the center's native unit of measure with no way to switch between seconds, minutes, hours, or days.

Changes

Calendar pages (WorkCenterCalendar, MachineCenterCalendar)

Added Capacity Shown In field in the Matrix Options group, positioned after View by
OnOpenPage initializes the field from \Manufacturing Setup.\Show Capacity In\ (with TestField guard, matching Work Ctr. Group Calendar behavior)
The selected unit is forwarded to the matrix via \Load()\

Calendar matrix pages (WorkCenterCalendarMatrix, MachineCenterCalendarMatrix)

Extended \Load()\ with a \SetCapacityUoM: Code[10]\ parameter (aligning with \Work Ctr. Grp. Calendar Matrix)
\MATRIX_OnAfterGetRecord\ now converts the \Capacity (Effective)\ flow field using \Shop Calendar Management.\TimeFactor()\ before assigning to the cell

#Load pages (WorkCenterLoad, MachineCenterLoad)

Added Capacity Shown In field in the Options group with \TableRelation = Capacity Unit of Measure.Code\ and OnValidate refresh
OnOpenPage initializes from \Manufacturing Setup.\Show Capacity In
The value is passed to the load lines subpage via \SetLines()
Load lines pages (WorkCenterLoadLines, MachineCenterLoadLines)
Extended \SetLines()\ with \NewCapUoM: Code[10]\ parameter (aligning with \Work Center Group Load Lines)
\CalcLine()\ applies the TimeFactor conversion to Capacity, Allocated Qty., and Availability After Orders
Load % remains a pure ratio and is unaffected by unit conversion

Pattern followed

All changes mirror the existing implementation in:

\Work Ctr. Group Calendar\ (page 99000771)
\Work Ctr. Grp. Calendar Matrix\ (page 9295)
\Work Center Group Load\ (page 99000891)
\Work Center Group Load Lines\ (page 99000892)

How I validated this

  • I read the full diff and it contains only changes I intended.
  • I built the affected app(s) locally with no new analyzer warnings.
  • I ran the change in Business Central and confirmed it behaves as expected.
  • I added or updated tests for the new behavior, or explained below why none are needed.

What I tested and the outcome (required — be specific: scenarios, commands, screenshots for UI changes)

Risk & compatibility

None

mazhelez and others added 4 commits July 8, 2026 10:39
… in calendar matrix and load lines

Machine Center has no "Unit of Measure Code" field. Both
MachineCenterCalendarMatrix (MATRIX_OnAfterGetRecord) and
MachineCenterLoadLines (CalcLine) referenced that non-existent field,
causing four AL0132 compile errors.

Fix: look up the parent Work Center via MachineCenter."Work Center No."
and use WorkCenter."Unit of Measure Code" as the TimeFactor numerator.
The existing else-branch (CapacityTimeFactor := 1 / raw cell value)
now also covers "Work Center No." = '' and a failed WorkCenter.Get,
so the guard is both correct and complete.

Also fixes a missing semicolon on the CapacityTimeFactor: Decimal
variable declaration in MachineCenterLoadLines.CalcLine.
…ace in Machine Center pages

MachineCenterCalendarMatrix and MachineCenterLoadLines now reference
Record "Work Center" after the UoM lookup fix. Both files are in the
Microsoft.Manufacturing.MachineCenter namespace, so the WorkCenter
table was unresolvable without an explicit using statement.

Add: using Microsoft.Manufacturing.WorkCenter
@Busslar Busslar requested review from a team July 8, 2026 09:45
@github-actions github-actions Bot added Build: Automation Workflows and other setup in .github folder From Fork Pull request is coming from a fork needs-approval Workflow runs require maintainer approval to start labels Jul 8, 2026
@Busslar

Busslar commented Jul 9, 2026

Copy link
Copy Markdown
Author

@Busslar please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.

@microsoft-github-policy-service agree [company="{your company}"]

Options:

  • (default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.
@microsoft-github-policy-service agree
  • (when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.
@microsoft-github-policy-service agree company="Microsoft"

Contributor License Agreement

Contribution License Agreement

This Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”), and conveys certain license rights to Microsoft Corporation and its affiliates (“Microsoft”) for Your contributions to Microsoft open source projects. This Agreement is effective as of the latest signature date below.

  1. Definitions.
    “Code” means the computer software code, whether in human-readable or machine-executable form,
    that is delivered by You to Microsoft under this Agreement.
    “Project” means any of the projects owned or managed by Microsoft and offered under a license
    approved by the Open Source Initiative (www.opensource.org).
    “Submit” is the act of uploading, submitting, transmitting, or distributing code or other content to any
    Project, including but not limited to communication on electronic mailing lists, source code control
    systems, and issue tracking systems that are managed by, or on behalf of, the Project for the purpose of
    discussing and improving that Project, but excluding communication that is conspicuously marked or
    otherwise designated in writing by You as “Not a Submission.”
    “Submission” means the Code and any other copyrightable material Submitted by You, including any
    associated comments and documentation.
  2. Your Submission. You must agree to the terms of this Agreement before making a Submission to any
    Project. This Agreement covers any and all Submissions that You, now or in the future (except as
    described in Section 4 below), Submit to any Project.
  3. Originality of Work. You represent that each of Your Submissions is entirely Your original work.
    Should You wish to Submit materials that are not Your original work, You may Submit them separately
    to the Project if You (a) retain all copyright and license information that was in the materials as You
    received them, (b) in the description accompanying Your Submission, include the phrase “Submission
    containing materials of a third party:” followed by the names of the third party and any licenses or other
    restrictions of which You are aware, and (c) follow any other instructions in the Project’s written
    guidelines concerning Submissions.
  4. Your Employer. References to “employer” in this Agreement include Your employer or anyone else
    for whom You are acting in making Your Submission, e.g. as a contractor, vendor, or agent. If Your
    Submission is made in the course of Your work for an employer or Your employer has intellectual
    property rights in Your Submission by contract or applicable law, You must secure permission from Your
    employer to make the Submission before signing this Agreement. In that case, the term “You” in this
    Agreement will refer to You and the employer collectively. If You change employers in the future and
    desire to Submit additional Submissions for the new employer, then You agree to sign a new Agreement
    and secure permission from the new employer before Submitting those Submissions.
  5. Licenses.
  • Copyright License. You grant Microsoft, and those who receive the Submission directly or
    indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license in the
    Submission to reproduce, prepare derivative works of, publicly display, publicly perform, and distribute
    the Submission and such derivative works, and to sublicense any or all of the foregoing rights to third
    parties.
  • Patent License. You grant Microsoft, and those who receive the Submission directly or
    indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license under
    Your patent claims that are necessarily infringed by the Submission or the combination of the
    Submission with the Project to which it was Submitted to make, have made, use, offer to sell, sell and
    import or otherwise dispose of the Submission alone or with the Project.
  • Other Rights Reserved. Each party reserves all rights not expressly granted in this Agreement.
    No additional licenses or rights whatsoever (including, without limitation, any implied licenses) are
    granted by implication, exhaustion, estoppel or otherwise.
  1. Representations and Warranties. You represent that You are legally entitled to grant the above
    licenses. You represent that each of Your Submissions is entirely Your original work (except as You may
    have disclosed under Section 3). You represent that You have secured permission from Your employer to
    make the Submission in cases where Your Submission is made in the course of Your work for Your
    employer or Your employer has intellectual property rights in Your Submission by contract or applicable
    law. If You are signing this Agreement on behalf of Your employer, You represent and warrant that You
    have the necessary authority to bind the listed employer to the obligations contained in this Agreement.
    You are not expected to provide support for Your Submission, unless You choose to do so. UNLESS
    REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING, AND EXCEPT FOR THE WARRANTIES
    EXPRESSLY STATED IN SECTIONS 3, 4, AND 6, THE SUBMISSION PROVIDED UNDER THIS AGREEMENT IS
    PROVIDED WITHOUT WARRANTY OF ANY KIND, INCLUDING, BUT NOT LIMITED TO, ANY WARRANTY OF
    NONINFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.
  2. Notice to Microsoft. You agree to notify Microsoft in writing of any facts or circumstances of which
    You later become aware that would make Your representations in this Agreement inaccurate in any
    respect.
  3. Information about Submissions. You agree that contributions to Projects and information about
    contributions may be maintained indefinitely and disclosed publicly, including Your name and other
    information that You submit with Your Submission.
  4. Governing Law/Jurisdiction. This Agreement is governed by the laws of the State of Washington, and
    the parties consent to exclusive jurisdiction and venue in the federal courts sitting in King County,
    Washington, unless no federal subject matter jurisdiction exists, in which case the parties consent to
    exclusive jurisdiction and venue in the Superior Court of King County, Washington. The parties waive all
    defenses of lack of personal jurisdiction and forum non-conveniens.
  5. Entire Agreement/Assignment. This Agreement is the entire agreement between the parties, and
    supersedes any and all prior agreements, understandings or communications, written or oral, between
    the parties relating to the subject matter hereof. This Agreement may be assigned by Microsoft.

@microsoft-github-policy-service agree company="GOB-Software-Systeme"

@Busslar

Busslar commented Jul 9, 2026

Copy link
Copy Markdown
Author

@microsoft-github-policy-service agree company="GOB-Software-Systeme"

@Busslar Busslar closed this Jul 9, 2026
@Busslar Busslar reopened this Jul 9, 2026
@github-actions

github-actions Bot commented Jul 9, 2026

Copy link
Copy Markdown
Contributor

Issue #9205 is not valid. Please make sure you link an issue that exists, is open and is approved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Build: Automation Workflows and other setup in .github folder From Fork Pull request is coming from a fork needs-approval Workflow runs require maintainer approval to start

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[BC Idea]: "Capacity shown in" on Work Center and Machine Center Calendar and Load

3 participants