From the Microsoft Dynamics AX blogs: Adding fields; Deleted sales orders; Exceeding number sequence; Task Recorder

A selection of the latest insight from the Dynamics AX blogs:

• Adding New Fields to the AX 2012 R3 Retail Distribution Sub-Jobs;
• Mark Deleted Sales Orders As Voided To Track Lost Sales;
• Number Sequence XXXX Has Been Exceeded;
• Making the Most of the Dynamics AX Task Recorder

Adding New Fields to the AX 2012 R3 Retail Distribution Sub-Jobs

On the K3 Retail Technical Blog, Malcolm Burtt says he's working on upgrading some of his company's AX 2012 R2 functionality to AX 2012 R3. One of the things he needed to do was port some code from the RetailConnSeedDataGenerator class.

In AX 2012 R2 this class performs a number of tasks to initialize the set up of the retail POS configuration, including creating default button groups and setting up the AX to Store database synchronization, Burtt explains. But the code required to get the synchronization set up in 2012 R2 was . . . well, a little inelegant, he says.

"When I came to port the code across to AX 2012 R3 I was expecting to find the same class and pretty much all the same methods so that [my] job porting the code would be pretty straightforward but when I looked at the R3 code I could [see] that the RetailConnSeedDataGenerator class had been substantially altered. It still sets up all the POS button groups, etc. but all of the code to initialize the data synchronization engine is gone."

You can find out what Burtt does next here.

Mark Deleted Sales ...

FREE Membership Required to View Full Content:

Joining MSDynamicsWorld.com gives you free, unlimited access to news, analysis, white papers, case studies, product brochures, and more. You can also receive periodic email newsletters with the latest relevant articles and content updates.
Learn more about us here

Get full access

or login