Notifications
Announcements
No record found.
Does anyone know if we have a current user guide for Purchase Requisition for GP2016?
*This post is locked for comments
Hi Larry,
I believe Microsoft stopped publishing GP manuals at version 2013.
Anyone else who knows otherwise, please chime in.Thanks!
R_Is, is correct.
The manuals stopped with 2013.
While it is true - it is a very sad thing to say that since Version 2013 we have not had any updates on the manuals. There are a ton of new features and rather than 'recreating an electronic file' Microsoft publishes 'Whats New' with each release. That leaves the consolidation of the 'whats new' since 2013 to now 2018 upto the client or the consultant.
I know many a time when I have been asked for a new manual, only to hum and haw and say well I will look into it. That is not really acceptable.
Come on Microsoft, we get the client to pay their annual maintenance, at the least update the manuals once every 3 versions of the software.
To add to this, it's correct that most of the documentation hasn't been updated since GP 2013, so to try and make up for that deficiency, we here on the GP Support team have been actively publishing at least one blog a day for a couple years now, which is also where you can find information on Purchase Requisition and other workflows (40+ blogs at last count just on the new Workflow functionality, including On Demand videos on how to set them up).
If you're not keeping an eye on the blogs already, you can do so at this link: community.dynamics.com/gp
I highly recommend the blogs as that is where we're now putting probably 95% of our information, to include a new feature blog series each time a new version of Dynamics GP comes out. Right now, we're planning on having blogs for new features for Dynamics GP 2018 R2 coming out probably around the first week of October.
In the blogs, we try to talk about new features, issues we're currently seeing, and 'how to' blogs to try and put as much information out to the public as we can.
That being said, we do understand the frustration of not having the documentation updated per GP version as that is what everyone is used to having.
Thanks
Derek, thanks for the information and while I understand that publishing new manuals will not likely happen - how about a quick update of the Electronic manual to at least remove reference to the VERSION - it would likely sit better with the client to see a 'published' manual that does not appear to be 5 plus years old, and then send them the link to the BLOG site - I could make that work. But when they see V2013 it is something I get called out on - out of date -
I will use the Blogs from now on - I will make it part of the review, implementation and training process to reference that site.
Thanks for a workable 'work around' to the problem.
Exactly, that's one of the things we on the support team have mentioned as well to try and get changed, is that, even if the documents aren't changing all that much, if at all, customers have questions when they see a 'GP 2013' document in their GP 2018 install, for example, so changing it to show the GP version in which the document is provided in, would save both calls to us and also calls from customers to partners as well.
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
As AI tools become more common, we’re introducing a Responsible AI Use…
We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…
These are the community rock stars!
Stay up to date on forum activity by subscribing.
Community Member 2
mtabor 1
Victoria Yudin 1