Microsoft Dynamics GP 2016 RTM

Microsoft Dynamics GP 2016 has reached the Release to Manufacturing (RTM) stage.

A little primer on Software Release Lifecycle: The term "release to manufacturing", known still as "going gold", is a term used when a software product is ready to be delivered or provided to customers. At this stage most if not all .NET assemblies and components are digitally signed, allowing the customers to feel confident about the integrity and authenticity of the software they are purchasing. A copy of the RTM build known as the "gold master" or GM is sent for mass duplication - nowadays, the majority of software products are downloaded from software distribution servers, but you still get the occasional vendor that ships DVD media. RTM precedes general availability (GA), when the product is released to the public.

Dynamics GP's GA is still scheduled for Sunday, May 1, 2016, at which point, customers and partners will be able to download from CustomerSource and ParterSource, respectively.

If you want to learn more about the enhancements and features in Microsoft Dynamics GP 2016, please come to GPUG Amplify in Anaheim, California. There's still plenty of time to complete your registration. Also, keep up with the Features of the day Series. I have summarized these by week for you, as follows:

Microsoft Dynamics GP 2016 Feauture of the Day Series - Week 1

Microsoft Dynamics GP 2016 Feauture of the Day Series - Week 2


You can find other articles on the web on Microsoft Dynamics GP 2016 RTM, at:

Inside Microsoft Dynamics GP
Dynamics GP 2016 Feature of the Day: Release to Manufacturing (RTM)

Until next post!

MG.-
Mariano Gomez, MVP

Comments

Microsoft Dynamics AX said…
I am more focused on microsoft dynamics ax but still nice that Dynamic GB had a release - it is really great software :)
May 10, 2016 at 8:45 AM
Post a Comment

Popular posts from this blog

DBMS: 12 Microsoft Dynamics GP: 0 error when updating to Microsoft Dynamics GP 2013 R2

Image
Hello all! It's been quite a while since I've actually written anything of remote interest to anyone who follows my blog, but at the same time, you will be pleased to know that I've been quite busy in the consulting front, with upgrades, server migrations, complex multi-instance postings involving 10's of thousands of transactions, wrapping up some Field Service Automation projects, and the list goes on and on. This time around I want to bring to the forefront, an issue I encountered updating  from Microsoft Dynamics GP 2013 SP2 to Microsoft Dynamics GP 2013 R2 plus the latest service pack. Background My client requested a server migration to a new environment where they wanted to deploy Dynamics GP 2013 R2 web client (plus the latest service pack) and upgrade their relational database management system to Microsoft SQL Server 2014. This is something I'm absolutely comfortable with (for the most part) given also that my client was sitting at Microsoft Dynamics...
Read more

Do I have to use those "Z-" currency IDs in GP?

Image
I know this seems like a trivia question, but recently I have come across a number of clients who have been using Microsoft Dynamics GP for a number of years and have been told by their former partners that they *must* use the predefined currency IDs created after adding the sample company, with no real explanation to support these claims. Case in point, my new client in Saudi Arabia, has been struggling for years to understand why they were told to prefix all currency IDs with the "Z-". So they went ahead and setup "Z-SR" for the Saudi Real. If you are familiar with Microsoft Dynamics GP and the sample company, Fabrikam, you may have noticed by now that after adding the sample company (which is not a requirement by any means), you will get a number of predefined currencies such as Z-US$ (US Dollars), Z-UK (British Pounds), Z-C$ (Canadian Dollars), Z-AUD (Australian Dollars), and so forth, accompanied by a number of exchange rate tables. If you are not familiar wi...
Read more

Microsoft Dynamics GP Scrolling Windows and Line Sequence Numbers

Image
I thought I would write about something meaningless that no one really thinks about. However, I realized that this is a compelling topic since it makes for some interesting discussion around the ability to insert line items withinin most transaction scrolling windows. Let’s take some time to understand where Line Sequence Numbers come from. A Line Sequence Number is auto generated by Dynamics GP and uses a seed value of 16,384 as a basis for the first line. Each subsequent line in the scrolling window is incremented by this number, so line number 2 would have a Line Sequence Number value of 32,768, line number 3 would have Line Sequence Number Value of 49,152, and so on. Since most GP transaction entry scrolling windows allow inserting rows in between line items, the newly inserted Line Sequence Number value is calculated as an average between the previous and the next line item sequences, i.e., if you were to insert an item in between row 1 and row 2 in the scrolling window -- keep in...
Read more