[Event Request] Add missing parameter to OnAfterCalcBaseQtyPerUnitOfMeasure in Codeunit 5402

Open Beginner friendly
#9,902 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Domain
backend

Research direction

Start in Codeunit 5402 by locating CalcBaseQty and OnAfterCalcBaseQtyPerUnitOfMeasure. Trace the event invocation for the Sales Line with another unit of measure, then update the event contract so QtyRndingPrecision is available. Done means the original precision can be checked by subscribers in that scenario.

Written by the indexing model from the issue text.

Description

event-request Team: SCM
Describe the issue

The mentioned event is missing the QtyRndingPrecision at procedure "procedure CalcBaseQty(ItemNo: Code[20]; VariantCode: Code[10]; UOMCode: Code[10]; QtyBase: Decimal; QtyPerUOM: Decimal; QtyRndingPrecision: Decimal; BasedOnField: Text; FromFieldName: Text; ToFieldName: Text) QtyRounded: Decimal". You have no oportunity to check the original QtyRndingPrecision.

Expected behavior

QtyRndingPrecision is passed.

Steps to reproduce

Create a Sales Line set an other unit of measure.

Additional context

Solution:
OnAfterCalcBaseQtyPerUnitOfMeasure(ItemNo, VariantCode, UOMCode, QtyBase, QtyPerUOM, QtyRounded,QtyRndingPrecision);

[IntegrationEvent(false, false)]
local procedure OnAfterCalcBaseQtyPerUnitOfMeasure(ItemNo: Code[20]; VariantCode: Code[10]; UOMCode: Code[10]; QtyBase: Decimal; QtyPerUOM: Decimal; var QtyRounded: Decimal;QtyRndingPrecision : Decimal)
begin
end;

I will provide a fix for a bug
  • I will provide a fix for a bug
Dominant language
AL
Stars
683
Forks
459
Avg merge
2d 20h
Merged PRs (30d)
621

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.

More from microsoft/BCApps

All issues in microsoft/BCApps

Similar issues

More Backend & API Design issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.