Following on from my post: Microsoft Dynamics GP 2013 R2 updates to Report Writer Functions , I have to admit that I made a mistake. The Problem The update to the RW_CoAddrIDInfo() report writer function has broken the code.
Violation of Primary Key constraint. Cannot insert duplicate key in object error when using Item List
Today, I have another blog post based on a recent support case. The partner logged a case with us where the customer was receiving the error “Violation of Primary Key constraint. Cannot insert duplicate key in object” when they used the Item List in Microsoft Dynamics GP
This week I had an interesting case from a partner trying to use the Capture Logins script from Knowledge Base (KB) article 878449.
I have been working on a recent support case that had a situation that makes me want to raise this topic again. In the past, I have posted a number of articles discussing reasons for connections to SQL Server to be lost.
I have seen this error pop up on a few Microsoft Dynamics GP 2013 systems, so I thought I would post some information to help you resolve it. …. Well, at least one possible cause of it
Happy New Year. Wishing everyone a very successful 2014. I have been back from leave for two weeks, but have been really busy with support cases
Developers: Microsoft Dynamics GP 2013 Service Pack 2 moves the Vendor and Customer Combiner & Modifier into core code
Now before you ask…. the answer is No, I have not spent all week playing XBox One (as mentioned on the last post )