Year: 2021

Across the years since it was launched I have done a lot of work with Management Reporter, including many migrations to new servers and upgrades which necessitated a migration to a new server or instance of SQL Server, but have never seen this particular error message before.

In this case, I migrated the Management Reporter database to a new server and installed the very latest version of the server software. When I started the database configuration, I received this error message:

Validation Messages
Database configuration: The connection to the database was successful, but the connection to database 'Management Reporter' failed. Verify that the Management Reporter service account has been added to the General User role in the database.

Continue reading “GeneralUser Error When Migrating Management Reporter to a New Server”

After creating a new script for updating vendor emails on test which includes the emails of sent items, I figured that a similar script will be needed to update the email address on sent emails in the Sales Series.

The script below, includes the tables holding sent email information for the Sales Series emails (both Receivables Management and Sales Order Processing) as well as the usual Internet Addresses table; the highlighted email address can be changed to whatever email address you’re using for testing your Sales emails:

/*
Created by Ian Grieve of azurecurve | Ramblings of an IT Professional (http://www.azurecurve.co.uk)
This code is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International (CC BY-NC-SA 4.0 Int).
*/
DECLARE @TestEmail VARCHAR(100)
SET @TestEmail = 'email@example.com'

-- UPDATE existing email addresses
UPDATE
	SY01200 --Internet Addresses (SY01200)
SET
	INET1 = @TestEmail
	,EmailToAddress = @TestEmail
	,EmailCcAddress = ''
	,EmailBccAddress = ''
WHERE
	Master_Type = 'CUS'
				
-- UPDATE Email Details of previously sent emails
UPDATE
	SY04910 --Email Details (SY04910)
SET
	EmailToAddress = @TestEmail
	,EmailCcAddress = CASE WHEN LEN(CAST(EmailCcAddress AS VARCHAR(1000))) = 0 THEN '' ELSE @TestEmail END
WHERE
	MODULE1 IN (9,11) -- Receivables Management / Purchase Order Processing
			
-- UPDATE Email Details of previously sent emails
UPDATE
	SY04915 --Email History (SY04915)
SET
	EmailToAddress = @TestEmail
	,EmailCcAddress = CASE WHEN LEN(CAST(EmailCcAddress AS VARCHAR(1000))) = 0 THEN '' ELSE @TestEmail END
WHERE
	MODULE1 IN (9,11) -- Receivables Management / Purchase Order Processing
GO

About 10 years ago I did a post on changing emails on the test system so they didn’t go outside the organisation. This has worked well for a long time and no-one has mentioned any issues, until this week when I was working with a client and we made some changes to a remittance format and tested by emailing.

The remittance itself emailed to the test address fine, but the reprint remittance went to the original email address of the vendor used on the live system.

After doing a little exploring I found there were two additional tables which held this data for sent emails and which were used by the reprint remittance function.

The script below, includes the Internet Addresses table as well as these two tables for the Purchasing Series emails (both Purchase Order Processing and Payables Management); the highlighted email address can be changed to whatever email address you’re using for testing your Purchasing emails:

/*
Created by Ian Grieve of azurecurve | Ramblings of an IT Professional (http://www.azurecurve.co.uk)
This code is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International (CC BY-NC-SA 4.0 Int).
*/
DECLARE @TestEmail VARCHAR(100)
SET @TestEmail = 'email@example.com'

-- UPDATE existing email addresses
UPDATE
	SY01200 --Internet Addresses (SY01200)
SET
	INET1 = @TestEmail
	,EmailToAddress = @TestEmail
	,EmailCcAddress = ''
	,EmailBccAddress = ''
WHERE
	Master_Type = 'VEN'
				
-- UPDATE Email Details of previously sent emails
UPDATE
	SY04910 --Email Details (SY04910)
SET
	EmailToAddress = @TestEmail
	,EmailCcAddress = CASE WHEN LEN(CAST(EmailCcAddress AS VARCHAR(1000))) = 0 THEN '' ELSE @TestEmail END
WHERE
	MODULE1 IN (12,19) -- Purchase Order Processing / Payables Management
			
-- UPDATE Email Details of previously sent emails
UPDATE
	SY04915 --Email History (SY04915)
SET
	EmailToAddress = @TestEmail
	,EmailCcAddress = CASE WHEN LEN(CAST(EmailCcAddress AS VARCHAR(1000))) = 0 THEN '' ELSE @TestEmail END
WHERE
	MODULE1 IN (12,19) -- Purchase Order Processing / Payables Management
GO

This post as been added as part of the series on creating a simple audit for Microsoft Dynamics GP, but wsn;t part of the original series.

I recently used the simple audit to add an audit to the Sales Customer Item Cross Reference (SOP60300) table to allow a client to keep an audit of changes to customer items. They wanted to keep track of all changes so this means three triggers are required on:

1. INSERT
2. UPDATE
3. DELETE

These triggers will record all customer items which are added, amended or removed. The Customer Items window contains a few fields, but the only ones with sensitive dta which needs to be audited are:

1. Customer Item Number
2. Customer Item Description

The first trigger creates the trigger which runs when data is inserted:

/*
Created by Ian Grieve of azurecurve | Ramblings of an IT Professional (http://www.azurecurve.co.uk)
This code is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International (CC BY-NC-SA 4.0 Int).
*/
CREATE TRIGGER utr_AZRCRV_SOP60300_AuditInsert ON SOP60300 AFTER INSERT AS
	INSERT INTO ut_AZRCRV_Audit
	SELECT
		'Sales Customer Item Cross Reference'
		,CAST(RTRIM(I.ITEMNMBR) AS VARCHAR(30)) + '|' + CAST(RTRIM(I.CUSTNMBR) AS VARCHAR(15))
		,'Insert'
		,SYSTEM_USER
		,GETDATE()
		,''
		,'Customer Item Number = ' + CAST(RTRIM(i.CUSTITEMNMBR) AS VARCHAR(30)) + ' | ' + 'Customer Item Description = ' + CAST(RTRIM(i.CUSTITEMDESC) AS VARCHAR(30))
	FROM
		inserted AS i
GO

Continue reading “Simple Audit for Microsoft Dynamics GP: Create Triggers for Audit of Customer Items”

This stored procedure can be executed to generate the next sequential sales document number; this script was created to get the next sales invoice number for a transaction to be inserted into Microsoft Dynamics GP through eConnect. I write stored procedures as a wrapper around the eConnect stored procedure as we are often working with the clients IT department or a third party and this abstracts the call way from the other application so any changes by Microsoft can be managed within the wrapper stored procedure rather than the application.

This particular example is for generating a sales order number, but can be used to generate a document number for any of the sales document transactions. To do this, change the first highlighted parameter to one of the following numbers:

1. Quote
2. Order
3. Invoice
4. Return
5. Back Order
6. Fulfillment Order

The second parameter should be set to the Doc ID which will vary depending on how you have configured Sales Order Processing.

The stored procedure to get the next sales document number is:

-- drop stored proc if it exists[/sqlgrey]
IF OBJECT_ID (N'usp_AZRCRV_GetNextSOPDocumentNumber', N'P') IS NOT NULL
	DROP PROCEDURE usp_AZRCRV_GetNextSOPDocumentNumber
GO
-- create stored proc
CREATE PROCEDURE usp_AZRCRV_GetNextSOPDocumentNumber AS
/*
Created by Ian Grieve of azurecurve | Ramblings of an IT Professional (http://www.azurecurve.co.uk)
This code is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International (CC BY-NC-SA 4.0 Int).
*/
BEGIN
	DECLARE @return_value INT
	DECLARE @I_tSOPType TINYINT = 2
	DECLARE @I_cDOCID CHAR(15) = 'STDORD'
	DECLARE @I_tInc_Dec TINYINT = 1
	DECLARE @O_vSopNumber AS VARCHAR(21)
	DECLARE @O_iErrorState INT
	
	EXEC @return_value = taGetSopNumber  @I_tSOPType = @I_tSOPType, @I_cDOCID = @I_cDOCID, @I_tInc_Dec = @I_tInc_Dec, @O_vSopNumber = @O_vSopNumber  OUTPUT,  @O_iErrorState = @O_iErrorState OUTPUT
	
	SELECT @O_vSopNumber 
END
GO

-- grant execute permission on stored proc to DYNGRP
GRANT EXECUTE ON usp_AZRCRV_GetNextSOPDocumentNumber TO DYNGRP
GO

You can execute the stored procedure using the below:

-- execute stored proc
EXEC usp_AZRCRV_GetNextSOPDocumentNumber
GO

I’ve written similar stored procedures in the past in other next numbers for other parts of Dynamics GP:

• Journal Entry Number
• Next Purchase Receipt Number
• Payables Voucher Number

I have also posted a custom solution which can be used to generate a next number when there isn’t a method available in eConnect.