Implementing Fastpath’s Assure Suite: Pre-installation steps

FastpathThis post is part of the series on Implementing Fastpath's Assure Suite.

When you place an order for the Fastpath Assure Suite, you are asked to complete a questionnaire; this is important to get correct as the details on this questionnaire will form the basis for both your registration key and how the Fastpath portal connects to your local system.

Once the questionnaire has been sent to Fastpath, they will create the necessary configuration on their side, including setting up the Fastpath portal; you will get both test and production portals created.

One of the details you’ll supply is the main administrator and how they will sign in (Microsoft Account or Fastpath account); along with your portal details you will also receive a log in to the support portal for the administrator.

Implementing Fastpath’s Assure Suite: What is Assure Suite?

FastpathThis post is part of the series on Implementing Fastpath's Assure Suite.

The Fastpath Assure Suite is a comprehensive security auditing tool for analysing segregation of duties, critical transactions and key access to systems. While it works with several systems, this series of posts is specifically looking at it working with Microsoft Dynamics GP.

Fastpath developed the Assure suite of tools to simplify security and audit needs by streamlining segregation of duties analysis and user access reporting. If your company is having trouble reviewing user access, recognizing access conflicts, or tracking what users do with their access, the Fastpath Assure suite has solutions to help. Separated into modules to allow proper reporting, the suite includes templates to make security or audit reviews easy to understand, shareable, and with scheduling automation, built for repeatable success.

Access Reviews

The Access Review module pulls user access data from your business software, allowing you to review and sign-off on access by user, company, role, and data sensitivity.

Audit Trail

The Audit Trail module tracks changes made to your business software, including schema changes. Audit Trail allows you design templates that focus on high conflict areas of change, creating efficient and easy-to-read reports.

Segregation Of Duties (SoD)

The SoD module analyses access in your business software by user or role, down to the lowest security level, reporting any conflicts or risks associated with the access.

Identity Manager

The Identity Manager module allows user provisioning to be fast and secure. Using this tool allows business process owners to request access directly from approvers without the need for IT intervention, streamlining the provisioning process. It also allows you to assign temporary (or firefighter) access.

Implementing Fastpath’s Assure Suite: Who are Fastpath?

FastpathThis post is part of the series on Implementing Fastpath's Assure Suite.

Before getting to the main subject of the FastPath Assure Suite, I thought it might be useful to give an overview of the company who develops it.

That company is Fastpath which is the leading provider of security, audit and compliance solutions for Microsoft Dynamics GP as well as the Dynamics CRM and the other Microsoft ERPs (it is also where my co-author and fellow Dynamics GP blogger Mark Polino works).

Fastpath’s products aim to simplify compliance and improve security with tools to manage segregation of duties, track database changes and integrate Dynamics security with Active Directory for better user and password management (part of this latter element is covered by the Config AD product on which I blogged six years ago.

The main product is Fastpath Assure which is the main subject of this series. In the next post, I’ll describe in more detail what Fastpath Assure is and why there is a benefit to using it.

Implementing Fastpath’s Assure Suite: Series Index

FastpathThis series of posts is on the Fastpath Assure Suite of products from Fastpath. I’ve dealt with this product a few times, but have recently implemented it twice, I thought a series of posts would be useful.

Over the course of the series, I will cover the installation and configuration of the Assure Suite, but with a specific focus on use of the Audit Trails module; I will return to the series in future and cover the use of the other modules.

Continue reading “Implementing Fastpath’s Assure Suite: Series Index”

Install Dynamics GP Web Services from the command line

Microsoft Dynamics GPI was giving a colleague a hand with a Microsoft Dynamics GP 2018 R2 upgrade recently (the client didn’t want to upgrade to the very latest version) and we encountered a problem with the installation of the Web Services:

Clr method invocation failed

Setup.exe .NET Framework Error

Clr method invocation failed

Continue reading “Install Dynamics GP Web Services from the command line”

Stored procedure to get next Dynamics GP Payables Voucher Number

Microsoft Dynamics GPI’ve previously posted SQL stored procedures to get the next GL Journal Number and the next PO Receipt number and today it is the turn of a stored procedure to get the next PM Voucher Number.

The stored procedure will call the eConnect stored procedure which gets the next number and increments the stored value. This code was written so I could easily call it from VBA in Integration Manager for an integration which needed to insert some data into a custom table. This allowed me to get the voucher number up front and use it in the VBA.

-- drop stored proc if it exists
IF OBJECT_ID(N'usp_AZRCRV_GetNextPMVoucherNumber', N'P') IS NOT NULL
    DROP PROCEDURE usp_AZRCRV_GetNextPMVoucherNumber
GO
-- create stored proc
CREATE PROCEDURE usp_AZRCRV_GetNextPMVoucherNumber AS
/*
Created by Ian Grieve of azurecurve|Ramblings of a Dynamics GP Consultant (http://www.azurecurve.co.uk)
This code is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike 2.0 UK: England & Wales (CC BY-NC-SA 2.0 UK).
*/
BEGIN
	DECLARE @return_value AS INT
	DECLARE @O_vCNTRLNUM AS VARCHAR(17)
	DECLARE @I_sCNTRLTYP AS TINYINT = 0
	DECLARE @O_iErrorState AS INT

	EXEC @return_value = taGetPMNextVoucherNumber
				, @I_sCNTRLTYP = @I_sCNTRLTYP
				,  @O_iErrorState = @O_iErrorState OUTPUT
				@O_vCNTRLNUM = @O_vCNTRLNUM OUTPUT
	SELECT @O_vCNTRLNUM AS VCHRNMBR
END
GO

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

The stored procedure can be executed using this command:

-- execute stored proc
EXEC usp_AZRCRV_GetNextPMVoucherNumber
GO

Dynamics GP Reconcile to GL missing the option for Inventory

Microsoft Dynamics GPI helped field a query from a client recently on the Reconcile to GL routine (Financial » Routines » Reconcile to GL) showing Payables Management, Receivales Management and Bank Reconciliation, but not Inventory.

This client has been a long time user of Microsoft Dynamics GP who had recently upgraded. This issue is a known one, addressed on the Dynamics GP Support and Services Blog.

With the support of the helpdesk, the client was able to run through the steps to resolve the issue and perform a reconciliation of the Inventory module to the GL.

Wildcard character in Dynamics GP Workflow conditions

Microsoft Dynamics GPI’ve done a lot of work with the Microsoft Dynamics GP Workflow module over the years since it was first released and it still seems to be growing in popularity with clients. Depending on the workflow type being created, the GL account string can be used in conditions to determine the routing for the approver.

However, commonly clients want to check the value for a single segment rather than the full account string. You can, to an extend, accomplish this using filters such as contains or begins with, but sometimes this isn’t feasible. You can get round this problem be using the _ wildcard in your condition.

For example, if I was setting up a purchase requisition workflow and wanted to configure a routing for all advertising expense codes, which is the codes where the Account segment start 66, to the Marketing Director, I could set up a condition where the account string is ___-66_0-00:

Workflow Condition error with wildcards in the account string

Workflow Condition example with wildcards in the account string

This would use this workflow step for all Divisions (segment 1) for department 00, where the Account (segment 2) starts with 66 and ends with 0. The wildcard character allows an account string with any value in the characters replaced with an underscore to be selected.

“The vendor has an existing purchase order…” error message when using Integration Manager

Microsoft Dynamics GPI’ve recently been working with a client to implement Microsoft Dynamics GP and have been using Integration Manager to import the opening data. While importing payables transactions I encountered the following error:

The vendor has an existing purchase order error

The vendor has an existing purchase order. Choose Continue to post or save. Choose Go To to view a purchasing navigation list. Choose Cancel to return to the window...

Continue reading ““The vendor has an existing purchase order…” error message when using Integration Manager”

SQL Stored Procedure to delete old Microsoft Dynamics GP Document Attachments

Microsoft Dynamics GPThe Document Attachment feature was introduced in Microsoft Dynamics GP 2013 RTM and has been enhanced a number of times since. One of the features it does not have is the ability to delete attachments; you can flag them as deleted, but they are not removed from the database.

With GDPR rules, clients have become concerned about the information retained in the system without a means to delete it. To that end I created a SQL stored procedure which could be scheduled to run on a regular basis and delete transactions older than the specified number of years (highlighted value is the number of years).

This allows clients to run this on a scheduled basis and remove old documents; it can also serve as the basis for a customised version which deletes on a more controlled basis.

As with any script, please ensure you perform through testing before deploying to a live system.

IF OBJECT_ID (N'usp_AZRCRV_DeleteDocAttachAttachments', N'P') IS NOT NULL
    DROP PROCEDURE usp_AZRCRV_DeleteDocAttachAttachments
GO

CREATE PROCEDURE dbo.usp_AZRCRV_DeleteDocAttachAttachments
	@iAge INTEGER = 7
AS
/*
Created by Ian Grieve of azurecurve|Ramblings of a Dynamics GP Consultant (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 TEMPORARY TABLE CREATE TABLE #AttachmentsToDelete( Attachment_ID CHAR(37) ) -- SELECT ATTACHMENTS OVER n YEARS OLD TO DELETE INSERT INTO #AttachmentsToDelete (Attachment_ID) --VALUES ( SELECT Attachment_ID FROM CO00101 WHERE CREATDDT < DATEADD(yyyy, -@iAge, GETDATE()) ) -- DELETE FROM Document Attachment Master (CO00101) DELETE FROM CO00101 WHERE Attachment_ID IN (SELECT Attachment_ID FROM #AttachmentsToDelete) -- DELETE FROM Document Attachment Reference (CO00102) DELETE FROM CO00102 WHERE Attachment_ID IN (SELECT Attachment_ID FROM #AttachmentsToDelete) -- DELETE FROM Document Attachment Properties (CO00103) DELETE FROM CO00103 WHERE Attachment_ID IN (SELECT Attachment_ID FROM #AttachmentsToDelete) -- DELETE FROM Document Attachment Status (CO00104) DELETE FROM CO00104 WHERE Attachment_ID IN (SELECT Attachment_ID FROM #AttachmentsToDelete) -- DELETE FROM Document Attachment Email (CO00105) DELETE FROM CO00105 WHERE Attachment_ID IN (SELECT Attachment_ID FROM #AttachmentsToDelete) -- DELETE FROM COATTACHMENTITEMS DELETE FROM coAttachmentItems WHERE Attachment_ID IN (SELECT Attachment_ID FROM #AttachmentsToDelete) -- DROP TEMPORARY TABLE DROP TABLE #AttachmentsToDelete GO