microsoft / AL

Home of the Dynamics 365 Business Central AL Language extension for Visual Studio Code. Used to track issues regarding the latest version of the AL compiler and developer tools available in the Visual Studio Code Marketplace or as part of the AL Developer Preview builds for Dynamics 365 Business Central.
MIT License
732 stars 243 forks source link

Possible overflow when creating Movement From Movementworksheet #6030

Closed ghost closed 4 years ago

ghost commented 4 years ago

Describe the bug In certain cases we receive an overflow error when creating a pick from the Movement worksheet. Works in English, in dutch (NLB) we receive the error.

Code: codeunit 7312 "Create Pick"

local procedure GetMessageForUnhandledQtyDueToBin(BinIsForPick: Boolean; BinIsForReplenishment: Boolean; IsMoveWksh: Boolean; AvailableQtyBase: Decimal; BinCode: Code[20]): Text[100] begin if AvailableQtyBase <= 0 then exit(''); if not BinIsForPick and not IsMoveWksh then exit(StrSubstNo(BinIsNotForPickTxt, BinCode)); if not BinIsForReplenishment and IsMoveWksh then exit(StrSubstNo(BinIsForReceiveOrShipTxt, BinCode)); end;

The Returned message is sometimes longer than 100 Characters and overflow is caused.

To Reproduce Steps and to reproduce the behavior: LocationFullWMS Create Fixed Bin for Item with min/max. Only create inventory for Item on Bin which allows no actions (not Ship, Not Receive, Not Pick, Not Putaway) Calculate The movement worksheet. Set application To NLB (Dutch). Will result in overflow error when creating movement.

Expected behavior No Error. Movement should be created.

Screenshots

5. Versions:

AL Language: 5.0.288712 Business Central: 16.2.13509.13779

qutreson commented 4 years ago

Let's get the issue to a team who will fix and backport it, as this repository is only for issues related to the AL compiler in latest developer preview environment for Dynamics 365 Business Central. We suggest that you open a support case or file a bug in Collaborate, to ensure that all Business Central users benefit from your catch as soon as possible.

To open a support case, you can:

If you file the bug in Collaborate, remember to include steps to reproduce the issue, and the Business Central build number and country version you're using.