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)

Batch WMS Picking route send XML fails

(0) ShareShare
ReportReport
Posted on by

I have a class that processes the picking lists with a status of "Activated" and sends these to the XML then updates the status to "Started".   This has been running for a number of years via batch without an issue.  About a month ago we started to have problems with some picking lists that, although they were updated as started haven't actually been sent to the AIF queue.  The code is as follows:-

if (wmsPickingRoute.canXMLBeSent())

        {
            wmsPickingRoute.sendElectronically(XMLDocPurpose::Original);

                wmsPickingRoute.ttsbegin();
                wmsPickingRoute.expeditionStatus = wmsExpeditionStatus::Started;
                wmsPickingRoute.StartDateTime      = DateTimeUtil::getSystemDateTime();
                wmsPickingRoute.operatorWorker     = DirPersonUser::findUserWorkerReference();
                wmspickingRoute.update();
                wmsPickingRoute.ttscommit();

        }

I know it has gone through this as the WMS picking route is updated to started but the lines are not - they still show as activated.  The pick list does not appear in the AIF Queue manager.  My user has System admin rights and I was the one to add the class to the batch queue.

If I run this on a client they process as expected.  The picklists that are failing are ones that have been posted to pick via another batch process.  I'm wondering if there is a security issue somewhere but as far as I'm aware nothing has changed in that area.  Any ideas of where to look would be appreciated.

Many thanks

Paulina

*This post is locked for comments

I have the same question (0)
  • Mea_ Profile Picture
    60,286 on at

    Hi Paulina Mudgway,

    If you can repro this issue you can put breakpoint and debug! That's the simplest way to find a root cause, otherwise it's hard to say what exactly is wrong without understanding what customizations and data you have.  

  • Verified answer
    Community Member Profile Picture
    on at

    Thanks for the reply - trouble is I can't repro this issue and I can't debug on the batch server. If I find the answer I'll post it here.

  • Mea_ Profile Picture
    60,286 on at

    It is possible to debug on batch server as well and there is msdn article explaining how to do this.

    However, if something could be done in client session but could not during batch execution there are usual suspects: CIL,  multithreading, 3rd party Dlls and access to resources . Its easy to check if CIL has been built for all AOSs and a bit harder to find if its caused any of reasons listed above.

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 39

#2
Michel ROY Profile Picture

Michel ROY 14

#3
imran ul haq Profile Picture

imran ul haq 8

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans