From the Microsoft Dynamics GP Blogs: DexNEXT; eConnect for SOP orders; Correcting posted journal entries; Australian Direct Entry

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

• Codename DexNEXT - Part 1 of 2;
• SOP Orders Imported With eConnect Auto Allocate and Auto Fulfill;
• How to Correct/Backout Posted Journal Entries in Dynamics GP;
• Australian Bankers Association Australian Direct Entry EFT File Format

Codename DexNEXT - Part 1 of 2

The Dynamics GP Blogster, better known as Mariano Gomez, says that readers of his blog have probably heard the codename DexNEXT at some point over the past year. DexNEXT represents a major milestone in the evolution of GP's Dexterity development platform and the Microsoft Dynamics GP application. Gomez notes that DexNEXT is predicated on the vision that Dynamics GP needs to consume as well as expose services to become a solid cloud offering.

"After all, when referencing "cloud," in reality we are referring the various services that live in the cloud. It is generally accepted that the Microsoft Dynamics GP 2013 web client is the first step in that direction.

"As such, starting with Microsoft Dynamics GP 2015, and to a certain extent, Microsoft Dynamics GP 2013 R2 the Microsoft Dexterity and Microsoft Dynamics GP development teams are evolving the core architecture to support services as a native component."

You can read about the key requirements driving this evolution here.

SOP Orders Imported With eConnect Auto Allocate and Auto Fulfill

On the Dynamics GP Land blog, Steve Endow says he received a call from a customer who has an