Hi all
We've been testing printing from AX and noticed that the AX service account is being sticked on the print job that's being added in the Windows print queue when printing in batch. This seems logical as the batch server process (ax32serv.exe) that runs under this user's context is probably adding the print jobs.
Problem: we kind of need the correct user id (from the end user that scheduled the print in batch) on that job to be able to couple this print task to this user's physical batch (follow me printer principle).
Anyone any ideas or experience with this?
I noticed D365 seems to have a solution for this: https://docs.microsoft.com/en-us/dynamics365/unified-operations/dev-itpro/analytics/install-document-routing-agent
But we're still on 2012R3 :-)
*This post is locked for comments
I have the same question (0)