Named Self Serve User: With GP2015 R2, we got a new user license namely “Self Service User”. With GP2016, named self service user license is introduced. In all honesty, I have to wait and see how this differentiate itself from the previous license model.
Automatically Batch Deposit Cash Receipts: This feature reduces one step and saves lot of time. Posting a cash receipt batch would automatically create a cash deposit (either by batch or by transaction, depending on the setup). Awesome.
Manage/Edit Attachment Flows: Allows us to edit the information that flows from master to transaction and more. Enhancements are always great.
Smartlist from Favourites: Users can now create a Smartlist from a favourite, retaining the search conditions and columns list. Great time saver.
Word Templates for Batch Approval Workflow: How about the ability to view the entire batch content before approving? That’s exactly what this feature is about. Excellent feature. This would further eliminate GP application dependency for trivial tasks.
Most important information among all that’s been posted, is the fact that we cannot perform a direct upgrade to GP 2016 from any version that’s lower than 12.00.1826. Not even those who are currently on GP 2013 R2 (12.00.1745). It has to be a two-step upgrade for all of them.
I am particularly excited about the last two in the above list; AA Access and Smartlist Designer Export/Import.
The gap between Smartlist Designer and Smartlist Builder is slowly (yet steadily) getting filled. While Smartlist Builder is one of its kind, Smartlist Designer now gives customers a lean version of Smartlist Builder that would satisfy most of the requirements. I am happy as a consultant that I now have an improved Smartlist Designer to talk about with customers/prospects.
I have had an interesting experience with one upgrade recently. While upgrading this customer’s GP to GP2015 R2, version check failed for one particular product. After going through the tables and SET file, I learned that the product in question was not part of DYNAMICS.SET and was not physically present in GP application folder. However, the SQL objects were very much present and DU tables had records for this product with quite an old version.
Customer informed that the previous implementer had installed this product, however in due course they realised that it was not required at all. Product was removed from the application environment, so there won’t be any necessary interference, however SQL objects and records remained.
It was a pain to clean up the records and continue with the upgrade process.
Beware of all possible scenarios and plan the upgrades well.
Account Framework Table Conversion – Tables getting converted are listed. This one’s crucial.
Database Compatibility – Make sure to change the compatibility level of all DBs (system & company DBs) to the version of upgraded SQL Server (SQL Server 2012 or SQL Server 2014). To my surprise, they have not mentioned about SQL Server 2016 yet. I know, SQL Server 2016 has not been released yet, however, I would have expected some kind of note somewhere that says GP2016 would support SQL Server 2016 once it is released.
Workflow Documents Must Be Final Approved – Please make sure that all workflow documents are final approved before running the upgrade. Would fail otherwise.
Overlapping Fiscal Periods – Make sure that you don’t have any overlapping fiscal periods by any chance.
One thing that I noticed (and got happy about) is that there’s no known issue mentioned about GP Web Client. I don’t know if we would have a separate post discussing the known issues. So far, I haven’t seen one, so I am happy that things would go well with HTML5 web client.