Click here to
Subscribe to
our Newsletter
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
Another Quick Tip for Dexterity developers. This one discusses what changes need to be made to an integrating Dexterity application when upgrading from pre version 10.0 code to version 10.0 or GP 2010 to handle the changes in the security model.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
An interesting tip today. Over the last few months there has been a thread on the Partner Forum (GP Notes Lockdown) with the request to prevent changes to the existing text on the Record Notes feature of Microsoft Dynamics GP.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
I came across an interesting issue yesterday relating to the Dexterity sum range command. We had a SQL datetime conversion error caused by a sum range command. This was the error message:
A sum range operation on table ‘SVC_Serial_Lot_Work_HIST’ failed accessing SQL data.
More Info: [Microsoft][SQL Server Native Client 10.0][SQL Server]Conversion failed when converting date and/or time
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
As I perform my role in the Asia Pacific Microsoft Dynamics GP support team I am finding that more and more sites already have the Support Debugging Tool for Microsoft Dynamics GP installed. This makes my job much easier as there are many features of the tool that help a support engineer diagnose and resolve technical issues.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
A couple of weeks ago, a good friend of mine posted on his Facebook account that his 1TB external hard drive had failed and that it contained a lot of data that was not stored anywhere else. In particular, there was 10 years worth of digital photos. All now lost.
I did have a look at the drive to see if it was something that could be recovered, but the problem was definitely a hardware failure with the drive failing to initialize. It would spin up the platters, but would make some very nasty noises when trying to perform the initial head seek. If my friend wanted to spend the money, it would be possible for a hard drive recovery specialist to recover the data by replacing the drive head assembly. However, as far as I know he has resigned himself to losing the photo collection.
So why am I telling you this little story?
Simple. As a warning.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
I had a case this week that was asking a fairly commonly asked question about integrating address information using eConnect. The scenario is that we want to update a customer or vendor address and the previous address had three lines in the address and the new address only has two lines. When the update is processed, Address Lines 1 and 2 have been updated, but Address Line 3 has the old data and has not been cleared.
So how can I update Address Line 3 with blank data?
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
A common question that new Dexterity developers have is what should they use for the version and build numbers when creating a chunk dictionary for distribution. This post discusses how those numbers are used and what the best practice for setting their values is.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
Following on from yesterday’s post: Quick Tip: Creating Dexterity System Variables, I want to cover a related issue.
This is when a Dexterity developer is creating a report (either new or alternate) which will display data from newly added tables. To get the data to show on the report the developer creates a table relationship from an existing Dynamics table to their newly added table.
Can you spot the problem yet?
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
Hi everyone.
This is another Quick Tip post for Dexterity developers. Vaidy’s recent post: “Illegal Address Field” Error while accessing a Global, raised the issue and so I thought I would respond with an explanation.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
I had a case a couple of weeks back, where the customer wanted to filter the transactions shown on a Receivables Management Statement. There was one type of transaction that they did not want included on the statements sent out to the customers. The transactions to be excluded could be identified by a particular value on the Description field on the transaction.