EDI Embedded in D365

ProcessOne has a long history with EDI.  Our first EDI installation was a custom system with Heinz in 1993. Before the days of readily available internet communications, this system relied on a dial up modem downloading EDI purchase orders from supermarkets as 4am, trucks being loaded in reverse drop off sequence and all trucks departing the warehouse by 9am. It worked from day one.

From that time until 2014, our EDI installations were with other people’s software.

By 2014 though we were getting disillusioned with available EDI software.

  • Most of the software was based on open system software. This is logical as most of the current players arose at the advent of the internet in the mid 90’s. As we’ve seen many times in the software industry, moving application software between technologies has proved to be the downfall of many software companies. For a lot of them it’s better not to try, stay with what you’ve got & milk it for as long as you can.

  • Microsoft released the .NET Framework in 2002 and the Azure Cloud in 2010. We started writing application software in .NET in 2002 and with the release of Azure, we felt the market was ready for an .NET/Azure EDI system.

  • The Microsoft technologies allowed ProcessOne to build a lot more automation into our software that was possible in the mid 90’s software. P1 is built around Web Services and XML, meaning P1 can update ERP systems automatically with inbound EDI transactions and can take receive XML from ERP systems to create outbound EDI transactions.

  • We released version 1 in 2014, our first customer, a beverage manufacturer in California went live in September 2014. We’re pleased to say they are still running P1 today. What was a relatively small operation at the time has now quadrupled in size and has expanded internationally to providing products to all the major supermarket chains in the UK. P1 has grown with our customer, initially all EDI transactions were X12, P1 is now processing EDI transactions through EDIFACT and Tradacoms as well. 

In 2017, we looked again at the Microsoft landscape and saw what Microsoft were doing with to move Dynamics AX into the cloud.

For ProcessOne, this meant that P1 and D365 would share a lot of common technology.

There were differences though

  • P1 was built in C#, HTML5 and a template web site

  • D365 is built in X++ and D365 UI controls

All advice we received from the Microsoft community was rebuild the front end of P1 in X++ and use the D365 UI. This is what we’ve done.

The EDI processing engine has been left in C#. This has been done to allow P1 to work both with D365 and other ERP systems.

So, if your customer runs D365 in one division and SAP in another P1 will process EDI transactions for them both.