RE: Why does GP have such SLOW reporting?
Hello Bob!
We hear your concerns!
In GP 2016, new historical tables were introduced in Bank Rec and so the reports were redesigned to now look at both the open and historical tables, and populate temp tables first to assemble the report, and yes, it does look at the whole table, so it is going to take longer, and the more data you have in the tables, the longer it will take. There were some improvements made in GP 2018 and have found that if you move some reconciled data to history, the reports do go faster. Here is the blog on how to do that:
https://community.dynamics.com/gp/b/dynamicsgp/archive/2016/12/22/microsoft-dynamics-gp-2016-r2-bank-reconciliation-reconciled-transaction-maintenance
Also, if you are printing the checkbook register, print it from the Inquiry window instead of the REPORTS menu. It goes much faster in the Inquiry window.
Some other options are to make smartlists, or even restore to a test company and remove some of the really old data from the CM20200/CM20300/CM30200/CM30300 tables if it goes back to 2002 and then you can run reports on newer data and it will go much faster. There are many options to get this information.
Dev resources are focused on bringing you new features and functions that are higher in priority. However, you can log a product suggestion too (or vote on one), as these are also reviewed from time to time to see what users want changed, so the number of votes will raise it up in priority. Here is the product suggestion link:
https://experience.dynamics.com/ideas/
So I recommend to make sure to move some data to history to see if this improves it, or even purge in a live or test environment. Print the checkbook register from the Inquiry window and it should go fast.
hope this information helps. Have a happy new year!
Cheryl Waswick
Microsoft Dynamics GP support
Share
Report
807
All responses (
Answers (
