web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Microsoft Dynamics AX (Archived)

WMS CU12: Stop error at trying to short pick with 0

(0) ShareShare
ReportReport
Posted on by

After upgrading from CU10 to CU12, one of our WMS customers get the following stop error message as they try to short pick with qty 0:

The container used in Map::create must contain at least 4 elements. (S)\Jobs\

This customer has no customizations. They do not use containerization/packing.

Short picking with larger quantities than 0 works, and also qty 0 worked before the upgrade to CU12.

We will analyse the code and see what the logic is or claims to be, and of course report it to Microsoft, but is there anyone else who has had this error? Is there a way around it that does not include installing a Microsoft hotfix?

*This post is locked for comments

I have the same question (0)
  • Community Member Profile Picture
    on at

    Hi,

    Could you reproduce that behaviour on a local environment (I mean, on your own environment, not in a customer's one)? This is to see if it could be a bug from CU12 or something that only happens on your customer.

    Could it be some step missed on the installation process? (run full CIL compilation, restart AOS services for example).

    I have experienced something similar, not in the "Short pick" option, but on a Purchase receipt menu after applying CU11 and the problem was the order in which the values were sent. In our case, before applying CU11, the user sent the PONum and LineNum at the same time, but after CU11 the PONum needed to be sent firtst and then the LineNum (clicking on "Ok" button each time).

    So, we only had to change the order on which the information was sent or submitted from the Mobile Device.

    This is the best I can do to help you.

    Regards.

  • Community Member Profile Picture
    on at

    Microsoft has confirmed the error as a standard bug. It was caused by another fix they did, KB3210293 with bug ID 3798382. The error is approved for fixing in LCS. The fix will be included in the Microsoft hotfix catalogue under the ID issue 3848493. I will be notified when the KB is ready to download.

  • Suggested answer
    Community Member Profile Picture
    on at

    Microsoft has confirmed the error as a standard bug. It was caused by another fix they did, KB3210293 with bug ID 3798382. The error is approved for fixing in LCS. The fix will be included in the Microsoft hotfix catalogue under the ID issue 3848493. I will be notified when the KB is ready to download.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the March Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
CP04-islander Profile Picture

CP04-islander 26

#2
imran ul haq Profile Picture

imran ul haq 8

#3
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 4 Super User 2026 Season 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans