Cancelling a purchase order line which came from a purchase requisition should, one would think, be a simple task. However, prior to Microsoft Dynamics GP 2016 R2, this was not necessarily the case.
This recently came back to mind when a client, who has recently implemented Purchase Order Processing with Workflow approvals on the requisitions (PO Entry window has been customised to lock a lot of the fields) raised an issue with me about not being able to cancel a line on the PO. After writing and demoing the functionality of Dynamics GP 2016 R2 a few times recently, it took a few minutes to identify a workaround for them as the client was running Dynamics GP 2015 R2 (14.00.1016).
The problem, is that you cannot cancel the link to the requisition in the same way you would a Sales commitment. If you try to cancel by entering a Qty Canceled, you get this error:
Microsoft Dynamics GP
The purchase order commitment can't be deleted; an attached sales line item is in use or is in history. Line items that weren't in use or in history are no longer committed to a purchase order.
Continue reading “Cancelling a PO Line Created From a Purchase Requisition”
This post is a PSA regarding an issue we encountered for a client recently while implementing Workflow approvals for Purchase Order Processing.
When the user received and opened the email notification with a View/Edit link, for some users the link displayed as a standard blue hyperlink, but it was not clickable, and for other users it just displayed as black text:
When I took a look at the source of the email, the a tag was empty:
After doing some testing on this, the problem appeared only to be the web based Outlook in Office 365; opening the same email in a desktop based Outlook client allowed the link to work correctly:
We logged this as a call with the Dynamics GP Support team, who were able to confirm out findings. The issue does not lie with Microsoft Dynamics GP; if it did the desktop Outlook client would not work either.
The issue is that Office 365 is stripping the link; I am assuming this is because it is not recognised as a valid link. It does not start http as a normal web link does, but with dgpp.
I have advised the client of this and suggested they speak to their Office 365 partner about logging this call with the 365 team and see what can be done in that area.
I am working with a client at the moment on a large scale roll-out of Purchase Order Processing with a large, complex Workflow approval process. The project started towards the end of the last financial year and into the current one. While users were performing UAT, an issue suddenly arose where a goods receipt notes could not be entered in Receivings Transaction Entry ( ). When the user tried, they received the following error:
Microsoft Dynamics GP
You cannot receive against unauthorised purchase orders.
Continue reading ““You cannot receive against unauthorised purchase orders.””
When reviewing some dashboards with a client a while ago we encountered an error launching the Financial Dashboard:
We found a problem with some content in 'T16R2 Financial Dashboard.xlsx'. Do you want us to try to recover as much as we can? If you trust the source of this workbook, click Yes.
Continue reading “Microsoft Dynamics GP 2016 R2 Financial Dashboard Error”
The below error message was reported to me by a user performing UAT (User Acceptance Testing) on an implementation of Purchase Order Processing and Workflow 2.0:
Microsoft Dynamics GP
You cannot print an unauthorized purchase order
This error was somewhat surprising as it was produced when trying to print a purchase order (PO) which had been converted from a purchase requisition (PR). There was a workflow process on the PR, which had been final approved and the PO created, but there was not a workflow on the PO.
I double checked to make sure that the old Purchase Order Enhancements (POE) Approvals functionality was disabled (it was) as the customer had previously been using this.
It was when I was checking for POE Approvals, that I realised that, as part of the project, we had enabled the PO Commitments part of POE.
The warning message was being produced as the PO line had exceeded the commitment budget value. Loading the PO, clicking the save button, accepting the override of the commitment budget value, reloading the PO and clicking the Print button successfully printed the PO.
eConnect is both a very useful tool for integrating data into Microsoft Dynamics GP, and also hugely frustrating. I assisted a client in creating a new test system recently and had some problems with eConnect. I installed it as normal, but the service didn’t start; when I tried to start the service manually, it started and immediately stopped without showing an error message.
I checked in the Windows Event Viewer for any errors and, again, there were none.
I’ve previously had issues with the eConnect service not starting and I figured it was worth a try.
The post linked above, has step by step screenshots, but the gist of what I tried is as follows:
- Make the eConnect service account an admin in Local Users and Groups.
- Start the service and note that it started correctly and continued to run.
- Stop the service
- Remove the eConnect Service from the Admins group.
- Start the service and again note that it started and continued to run.
The service has continued to run correctly since then.
I’ve been doing some work recently on upgrading some Dexterity code to work with Microsoft Dynamics GP 2016 (both the RTM and R2). After compiling the new dictionary, I started Microsoft Dynamics GP and as the home page was loading got the following error:
Unhandled script exception:
SCRIPTS - data area
Continue reading “Dexterity Development ‘Unhandled script exception’ on data area”
A client who had recently upgraded to Microsoft Dynamics GP 2016 reported an error when approving a purchase order via Workflow 2.0 Email Actions. The user would click Approve on the email, enter their comment and click Approve and then received the following message:
The server encountered an error processing the request. See server logs for more details.
The purchase order was showing as approved, so Workflow itself was working correctly from this point of view and I couldn’t find any logs which might explain the issue.
However, while I was having a look at the workflow setup, I noticed that the Purchase Order Approval workflow type, did not have a manager set. There had been a workflow manager defined or the workflow process could not have been activated, but at some point it disappeared.
Adding a manager for the workflow type, saw the error message stop appearing.
The manager’s disappearance could be related to the upgrade, but I’ve upgraded some other clients who were using workflow and not had his same problem.
I was onsite with a client to start a project implementing Workflow 2.0 for Purchase Requisition Approval and ran into a problem while doing training on how to interact with the workflow.
Everything had been fine until this point, but after creating a simple example approval workflow, I clicked the Submit button on the Purchase Requisition Entry window and nothing happened; I tried again through the navigation list, again without success.
I promised to figure out the issue in the next break and moved onto discussing other ways of interacting and then called the break.
It occurred to me that this might be another manifestation of an issue I have encountered previously, but without the visible error message.
I ran the script against the system database which redeploys the .NET Assemblies used by Workflow:
It took a few minutes to run through, but I was then able to approve the requisition without further problem.
Just before Christmas I was creating an integration for a client in Integration Manager which would integrate Sales Orders, but unfortunately I was receiving an error message:
Integration: Eriks SO Integration (ID: 8)
Start Time: 23/12/2016 11:05:38
23/12/2016 11:05:38 Source: IIntegrationEngine_Run, Status Code: 0 Opening source query...
23/12/2016 11:05:38 Source: IIntegrationEngine_Run, Status Code: 0 Initializing Source...
23/12/2016 11:05:38 Source: IIntegrationEngine_Run, Status Code: 0 Establishing source record count...
23/12/2016 11:05:38 Source: IIntegrationEngine_Run, Status Code: 0 Beginning integration...
1: Order Insert Failed 5. Seconds
DOC 1 ERROR: The Sales Intrastat Entry window is open. - The Sales Intrastat Entry window is open.
23/12/2016 11:05:43 Source: FinishIntegration, Status Code: 3 Integration Failed
23/12/2016 11:05:43 Source: FinishIntegration, Status Code: 3 Integration Results
1 documents were read from the source query.
1 documents were attempted:
0 integrated without warnings.
0 integrated with warnings.
1 failed to integrate.
Finish Time: 23/12/2016 11:05:43
Source Total: 1
Successfully Integrated: 0
Integrated With Warning: 0
Completion Status: Completed
Integration Status: No Documents Succeeded
Continue reading “Integration Manager Sales Order Integration – “The Sales Intrastat Entry window is open””