End of mainstream support for Microsoft Dynamics AX 2009, 2012, and 2012Mainstream support for Dynamics AX 2009 Service Pack 1 (SP1), Dynamics AX 2012, and Dynamics AX 2012 R2 ended Oct. 9, 2018. After that date, only security hotfixes will be provided for these three versions through the extended support period that until Oct. 12, 2021. Read more
2019 release wave 2 Discover the latest updates to Dynamics 365Release overview guides and videos Release Plan | Early Access Availability
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Talent TechTalks
We have implemented the Workflow Email Approval system for AX 2012 R3 CU9 in a test system and it functions without issue. Our customer has since gone live and we have changed the Connector for Mobile Apps configuration to point to the second AOS for the PROD system. The Connector lives on another server and I just changed each endpoint in the connector to point to AOS-2. Their system currently has 2 AOS's and the workflow batches run on AOS-2. The email gets sent to the user with the accept / reject links in it. When the user clicks the Accept link, it puts the following message up on the screen "This purchase requisition has already been approved" but when the user either goes through the Enterprise Portal or the AX client, the Purchase Requisition is still "in review". Any thoughts? Again, we are running R3 CU9 and the mobile connector is 8.2.379.0.
might be helpful, blogs.msdn.microsoft.com/.../workflow-approval-via-email-shows-incorrect-responses
I figured it out. I could not get the connector to run on the PROD AOS-2 server to begin with so all I did was redirect the working connector to use the AOS-2 system. I had read a while back that you need to run the connector on the actual AOS server that it is interfacing with. Once I added the user that was running the connector service (the BC Proxy user) to the local admins on the server, the service started and I was able to open the Mobile Connector console and configure it. Once configured and running on the PROD AOS-2 server, users were able to approve requisitions. Thank you!
Business Applications communities