I have seen many requests recently for a way to see what Dynamics GP vendors have had no recent activity. Since ‘recent’ can mean different things, I thought I would put together a view that shows the last activity date for each vendor.
You can find this document, as well as a sample report using each one of these functions in the GP Software Development Kit (SDK) You can find the SDK in the Tools folder of the DVD installation media. The functions are separated into four different categories: Numeric Functions String & Text Functions Date & Time Functions Data Functions Multicurrency Functions Below is a listing of each function and how to use it: Numeric RW Functions RW_Abs Module: System Manager Series: System Script type: Global function Form (If a form global): Category: Numeric Manipulation Description: Returns the absolute value for the currency or vcurrency value supplied
No, my post title it’s not an official slogan for the conference, but the reIMAGINE 2014 conference in Fargo promises to be just what Microsoft Dynamics GP partners had been expecting for years: and all out sales, technical consulting, and software developer extravaganza that combines the likes of the former Great Plains Software’s Stampede to Fargo and the Microsoft Dynamics GP Technical Airlift. But there’s a caveat: as a partner, YOU get to provide feedback on the content and topics you want to see and learn about
"Invalid Object Name ..SY01500" error after restoring GP 2013 company database in a different environment
Just recently I was working with a partner to determine the root cause of an issue that stemmed from restoring a company database from a customer’s production environment, to the partner’s development environment. After restoring the database, we could see the following error messages attempting to access the database: Invalid object name SY01500 error smCleanupFilesBeforeLogin stored procedure error Login failed error Enabling a DEXSQL.LOG gave us more insight into the issue. We could see the following prepared statement being executed prior to the ODBC error message: /* Date: 05/18/2014 Time: 19:55:37 stmt(148745784):*/ BEGIN DECLARE @stored_proc_name char(34) DECLARE @retstat int DECLARE @param5 tinyint DECLARE @param6 smallint DECLARE @param7 tinyint DECLARE @param8 tinyint DECLARE @param9 tinyint DECLARE @param10 tinyint DECLARE @param11 tinyint DECLARE @param12 int set nocount on SELECT @param5 = 0 SELECT @stored_proc_name = ‘ZBPI.dbo.smCleanupFilesBeforeLogin’ EXEC @retstat = @stored_proc_name 5, ‘sa’, ‘ Company_Name ‘, 0, @param5 OUT, @param6 OUT, @param7 OUT, @param8 OUT, @param9 OUT, @param10 OUT, @param11 OUT, @param12 OUT SELECT @retstat, @param5, @param6, @param7, @param8, @param9, @param10, @param11, @param12 set nocount on END /* /* Date: 05/18/2014 Time: 19:55:37 SQLSTATE:(S0002) Native Err:(208) stmt(148745784):*/ MicrosoftSQL Server Native Client 10.0SQL ServerInvalid object name ‘DYNGP2013..SY01500′.*/ /* The prepared statement calls the dbo.smCleanupFilesBeforeLoging stored procedure, which has (68) hardcoded references to the former system database in the old environment
Dex.ini settings have always existed to provide developers and end-users with ways to set a number of preferences for their Microsoft Dynamics GP application without the need of additional development or customizations. With the release of Microsoft Dynamics GP 2013 and the web client, the Dex.ini now plays a key role in enabling (or disabling) certain elements rooted in the system’s architecture itself.
Preventing Visual Studio Tools customization processes from being terminated by Microsoft Dynamics GP
Just recently I ran into a case on the Microsoft Dynamics GP partner forum where the ISV developer was dealing with a potentially long standing process to be executed from within their Visual Studio Tools (VST) add-in customization.
I was talking with some resellers this week who were excited about how easy it was to sell SmartView into their customer base. The problem was, they said, that it was difficult to include services in the software quote because SmartView was just too easy to set up