Click here to
Subscribe to
our Newsletter
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
A couple months ago there was a post on the Partner Forum about Dexterity Oddities. One of the points raised in the post was about passing a text datatype parameter to a procedure called in the background and the fact that the contents of the text variable are lost. The same code called in the foreground works.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
This quick tip follows on from my previous post: Quick Tip: Updating Dexterity customizations to work with Security Tasks and Security Roles.
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.
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.
I am wondering if Joseph Tews is a mind reader, or if he can somehow see my draft blog posts before they are published. Joking aside, it turns out that the same day he posted about Symantec Endpoint Protection, he also posted about this topic that I was planning to post about. Unless he has a super power, then I will have to believe that these issues are faced by enough people to warrant multiple blog posts.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
I recently had a case where the customer was able to install the Microsoft Dynamics GP client on a machine, but when they clicked on the shortcut nothing happened. Even dragging the DYNAMICS.SET launch file onto the DYNAMICS.EXE application did nothing. In fact, any thing that involved getting the Dexterity Runtime Engine DYNAMICS.EXE to launch failed.
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?