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
Dynamics 365 2019 release wave 2 plan Discover the latest updates to Dynamics 365.Release Plan | Weekly Deployment Notes
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
In a previous post we touched on the concept of the OCI protocol and how that is used in the punch out scenario. This video goes through the setup on the external catalog to handle the punch out and specifically you want to pay attention to the setup of the protocol. This will require a review in your requirements phase and testing to see if this will handle all the suppliers that you want to punch out to. Good chance if you have many suppliers you will have to customize a class of your own by copying the sample class to implement a message handler.
In this video I’m using R3 but this configuration is the same with any version of AX2012. If you didn’t catch the sample class name in the video it’s Sample_Code_CatMessageFormatterOCI40HTML. The table where you want to modify the protocol name to be able to specify it in the form is CatExternalMessageFormat
Business Applications communities