Author: Ian Grieve

This post is part of the series on Implementing Fastpath's Audit Trail and is part of the parent Implementing Fastpath's Assure Suite series.

A couple of psots ago I covered the creation of triggers for auditing information. This allows you to create any trigger you want, but can be a somewhat long-winded way of doing things. Fortunately, Fastpath provide a number of templates which you can apply as a shortcut.

To apply a template, click (Tools » Templates) on the application menu:

Continue reading “Implementing Fastpath’s Audit Trail: Apply templates”

This post is part of the series on Implementing Fastpath's Audit Trail and is part of the parent Implementing Fastpath's Assure Suite series.

Once you have tables selected for auditing, the next step is to create the triggers in the database. To create the triggers, click the Create Triggers button on the toolbar:

Continue reading “Implementing Fastpath’s Audit Trail: Create Triggers”

This post is part of the series on Implementing Fastpath's Audit Trail and is part of the parent Implementing Fastpath's Assure Suite series.

Audit Trails tracks changes by creating triggers on SQL Server. When you create the triggers you do so by selecting a table, choosing the events to track and which fields to be audited:

You can separately choose to track inserts, updates and deletes by marking the relevant boxes, although in most cases you would want to track all three.

Next you can select any of the fields on the table for auditing; I’d recommend against tracking everything as this can make the audit data very large and if there are fields you don’t populate or aren’t important, then there is no point auditing them.

Likewise, you can audit as many tables as you want, but I’d recommend against auditing all tables as this can have an impact on performance. I’d also recommend against auditing transaction tables due to the volume of data which would pass through them.

In the next post, I’ll show how to apply the triggers for the selected tables and fields.

This post is part of the series on Implementing Fastpath's Audit Trail and is part of the parent Implementing Fastpath's Assure Suite series.

While Audit Trails allows you to audit changes to any SQL Server database. When you first log into Audit Trails you will be prompted to login and select a database:

Continue reading “Implementing Fastpath’s Audit Trail: Select company to audit”

This post is part of the series on Implementing Fastpath's Audit Trail and is part of the parent Implementing Fastpath's Assure Suite series.

The Audit Trails software can be installed on any machines necessary and connect to the same SQL Server database. Users need to be granted access to Audit Trail in order to access the application. To do this, log into Audit Trail and click (Tools » Grant AT Access):

Continue reading “Implementing Fastpath’s Audit Trail: Grant AT Access”

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

The final step of the Fastpath Assure portal configuration is to schedule the collect of data for Audit Trails

To do this, log into the Fastath Assure portal and in the navigation pane select (Audit Trail » Setup » Manage Data) and click the calendar button.

Select the frequency and configure the other options (which change depending on the frequency) and click Schedule:

In the above example I have set a daily frequency with the collect happening at 0500.

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

The penultimate step of the Fastpath Assure portal configuration is to schedule the automatic security import.

Log into the Fastpath Assure portal, expand Integrations, select Connections and click the calendar icon.

Set the required Frequency and Time and then click Schedule:

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

With the Hybrid Connection Manager configured, the next step of the configuration is to update the portal with the server settings. Log into the Fastpath Assure portal (or here if you’re in the UK), select Integrations and click Connections.

Click the cog icon and fill in the details for the GP Connection Settings; even if you’re using a named SQL Server instance, you can leave this box empty.

if you’re using Identity Manager, select your version of Microsoft Dynamics GP, selecting GP 2016 for that or any later version.

Click Save to save the changes:

Continue reading “Implementing Fastpath’s Assure Suite: Setup cloud connection”