A client on Dynamics GP 2010 R2 has been configuring email for the RM statements recently, but after configuring the system were still receiving an error message:
Path for the E-mail Status Report is Not Setup
When we were assisting to diagnose the problem, we found that while they did have the EmailStmtStatusPath line in their Dex.ini file (as detailed in this KB article), the specified path did not have a trailing slash; as soon as this was done the report started working without issue.
The Inside Microsoft Dynamics GP blog has started a series of posts on the new features of, the soon to be released, Microsoft Dynamics GP 2015. As I have done for the last two releases, I intend to shadow these posts and add my own opinions on these new feature; the series index is here.
The thirty fifth Feature of the Day is Existing Purchase Order Warning. A new warning message has been added to the Payables Transaction Entry form to prompt the end-user if they attempt to post or save an invoice for a vendor that already has an available Purchase Order in the application:
This new functionality will be disabled by default on upgrades but can be enabled by selecting the Warn if Vendor has Existing Purchase Order checkbox on the Payables Management setup window. For new installs, the functionality will be enabled by default.
It has always been a bit of a debate as to how non-PO invoices should be entered into Dynamics GP; do you use Payables Transaction Entry () or enter a Shipment/Invoice in Receivings Transaction Entry (). Most clients have opted to use Payables Transaction Entry which means this new warning message could be very useful for preventing the entry of payabes invoices when there is an outstanding PO.
The roles targeted by this feature are:
The Inside Microsoft Dynamics GP blog has started a series of posts on the new features of, the soon to be released, Microsoft Dynamics GP 2015. As I have done for the last two releases, I intend to shadow these posts and add my own opinions on these new feature; the series index is here.
The thirty fourth Feature of the Day is Employee Self Service Purchase Requisitions. Dynamics GP 2015 Purchase Requisitions lets a user enter a requisition which ties in with Purchase Order Processing functionality.
Â
As part of the Employee Self Service functionality, navigation is streamlined for the requester to see a requisition status or enter a requisition.
Â
Users are able to quickly see important information right from their Home Page using the Saved, Ready for Purchase, Pending User Action, Rejected Workflow, and Approval tiles:
Continue reading “MDGP 2015 Feature of the Day: Employee Self Service Purchase Requisitions”
The Inside Microsoft Dynamics GP blog has started a series of posts on the new features of, the soon to be released, Microsoft Dynamics GP 2015. As I have done for the last two releases, I intend to shadow these posts and add my own opinions on these new feature; the series index is here.
The thirty third Feature of the Day is Management Reporter Data Integration. In Microsoft Dynamics GP 2015, the user can determine the data that is available to the Microsoft Dynamics Management Reporter DataMart, improving the performance and giving the user control over the data selected.
Â
The user can choose per company (including sample company) if they want the General Ledger data available for reporting.
Â
The user also has the ability to include or exclude Analytical Accounting data for each company:
I am slightly puzzled by this feature of the day as you can simply not import a company into Management Reporter if you don’t want to report on it. While I steer clients away from AA where possible, I am not entirely opposed to it, but I do wonder who would want to report on AA without also wanting to be able to report on the GL.
The roles targeted by this feature are:
The Inside Microsoft Dynamics GP blog has started a series of posts on the new features of, the soon to be released, Microsoft Dynamics GP 2015. As I have done for the last two releases, I intend to shadow these posts and add my own opinions on these new feature; the series index is here.
The thirty second Feature of the Day is Project Employee Expense Entry. Project Accounting employees can create expense reports for any projects to which they are assigned. Employees can also be set up to allow delegates to enter expense reports on their behalf.
Workflow approvals and task assignments are defined for expense reports; workflow actions are executed on the documents from the Expense Entry window or from the Navigation lists.
Continue reading “MDGP 2015 Feature of the Day: Project Employee Expense Report Entry”
The Inside Microsoft Dynamics GP blog has started a series of posts on the new features of, the soon to be released, Microsoft Dynamics GP 2015. As I have done for the last two releases, I intend to shadow these posts and add my own opinions on these new feature; the series index is here.
The thirty first Feature of the Day is Void Intercompany Journal Entries. In Microsoft Dynamics GP 2015, one of the improvements to the intercompany functionality is the ability to view the intercompany distributions of a journal entry from another company.
Having the Intercompany Journal Entry Inquiry window eliminates the need for users to switch between companies to view all originating- and destination-company distributions of an intercompany journal entry. All distributions can be viewed from one company.
The Intercompany Journal Entry Inquiry window is launched from the Journal Entry Inquiry () using the Intercompany button at the bottom of the window:
Continue reading “MDGP 2015 Feature of the Day: Intercompany Journal Entry Inquiry”
I ws recently doing some work for a client, one part of which was to configure Microsoft Dynamics GP to duplicate creditors created in one company into another using the PM Master Trigger functionality in the Professional Services Tools Library (PSTL).
When I tried to enable the trigger I received the following error message:
Microsoft Dynamics GP – The stored procedure failed to enable taVendorInsert returned the following results: DBMS: 4920, Microsoft Dynamics GP: 0Continue reading “Professional Services Tools Library – DBMS Error 4920”
The Inside Microsoft Dynamics GP blog has started a series of posts on the new features of, the soon to be released, Microsoft Dynamics GP 2015. As I have done for the last two releases, I intend to shadow these posts and add my own opinions on these new feature; the series index is here.
The thirtieth Feature of the Day is Edit Email on Historical Transactions. In Microsoft Dynamics GP 2015 when you want to send an e-mail for a historical document you can add additional e-mail addresses and choose which e-mail addresses you wish to send to.
On Navigation Lists, you can mark a group of historical documents and e-mail them to a different e-mail address. So, if a customer wants a copy of a number of invoices, you can mark them, and e-mail them to the specific address.
Edit E-mail Detail is available for Receivables statements, Sales Order transactions, Purchase Orders and Payables remittances:
Continue reading “MDGP 2015 Feature of the Day: Edit Email on Historical Transactions”
The Inside Microsoft Dynamics GP blog has started a series of posts on the new features of, the soon to be released, Microsoft Dynamics GP 2015. As I have done for the last two releases, I intend to shadow these posts and add my own opinions on these new feature; the series index is here.
The twenty ninth Feature of the Day is Void Intercompany Journal Entries.In Microsoft Dynamics GP 2015, users will have the ability to void an intercompany journal entry, including entries posted in destination companies, by voiding the original entry in the originating company. This eliminates the need to void an entry in both the originating company, and individually in each destination company as separate steps. When the user voids the entry in the originating company, intercompany entries are also created automatically in destination companies to void the original intercompany entries.
The roles targeted by this feature are:
The Inside Microsoft Dynamics GP blog has started a series of posts on the new features of, the soon to be released, Microsoft Dynamics GP 2015. As I have done for the last two releases, I intend to shadow these posts and add my own opinions on these new feature; the series index is here.
The twenty seventh Feature of the Day is Business Analyzer Cross Platform. This features enables tablet users on Windows, iOS or Android to install and use the Microsoft Dynamics Business Analyzer app.
Microsoft Dynamics Business Analyzer is a cross Dynamics Business Intelligence app that enables AX, GP and SL customers the ability to view and take action on key business information right at their fingertips.
Microsoft Dynamics Business Analyzer was initially released in January 2013 to the Windows Store. The application has been a huge success within the Dynamics community with over 20,000 downloads since the initial release! We are excited about the continued success of the app as we expand its availability to more platforms and devices.
The roles targeted by this feature are: