Tag: Fastpath

In yesterdays post on encountering an error deploying the Fastpath Audit Trails to a new company, there was a problem which came up, but I forgot to mention.

When the minimum permissions script (also know as the hybrid grant script) from Fastpath was run, an error in SSMS was produced which was not seen when implementing:

Msg 3729, Level 16, State 1, Procedure sp_revokedbaccess, Line 51 [Batch Start Line 18]
Cannot drop schema 'Fastpathsql' because it is being referenced by object 'GP_DR_AT_BankDetailChanges'.

The problem here was because we had created a report via the portal and this had the owner of the SQL login configured for use by Audit Trails. The solution is to change the database owner to dbo.

This can be done a few ways, but the “safest” is to use the sp_changeobjectowner stored procedure to alter the owner to dbo:

EXEC dbo.sp_changeobjectowner @objname = 'Audit Trails SQL Login.SQL view name', @newowner = 'dbo'

The two highlighted sections need to be replaced; the first with the current owner of the view, the second is the view name.

I implemented Audit Trails from Fastpath for a client a while ago. They created the required triggers in a few company databases and all worked well.

Recently they deployed the triggers to another company, but none of the data was flowing through to the portal.

I did some investigation and found the triggers were working correctly as the audit tables in the company database were being populated, but the data collect wasn’t moving them to the audit table in the FPAUDIT database. Further investigation and a quick suggestion from the Fastpath support team had me checking permissions on the databases; the database triggers were being added to did not have the required permissions for the Fastpath SQL login.

When I checked with the user, this was a company created after the initial deployment of Audit Trails and so the user had never had permissions to this database. We re-ran the minimum permissions script and the data collect was then able to run successfully and collect the audit changes from the new company.

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.

In yesterday’s post, I took a look at the Data Changes view available in the Fastpath Assure portal for Audit Trail. This is the way of looking at the raw data, but is not the friendliest method of reviewing the audited changes which is available, It is suitable for someone like me who understands the data structure of Microsoft Dynamics GP, but the ordinary end-user needs something more user friendly.

Fortunately, this is available from the reports which are included as standard. To access these reports, expand Audit Trails and select Reports; there is a long list of reports then shown in the navigation pane:

Continue reading “Implementing Fastpath’s Audit Trail: View reports”

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.

With Audit Trails installed, configured with triggers created and a scheduled data collect in place, the audited changes are available for users to view in the Fastpath Assure portal.

The first palc you can see them, and the one covered in this post, is in Data Changes (accessible from (Audit Trail » Data changes):

Continue reading “Implementing Fastpath’s Audit Trail: Review data changes”

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.

Ina previous post I covered the scheduled collection of Audit Trails data. This will allow you to schedule a regular collection of data which, for example, may run every day in the early hours, but sometimes you might need to audit ome data same day. To facilitate this, the Assure portal includes an ad hoc data collection routine for Audit Trails.

To run this ad hoc collect data, select the Manage Data page (Audit Trail » Setup » Manage Data) and click the arrows button.

Clicking the Collect button will run the data collection and pull all new data through to Fastpath:

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

In the last post, I showed how to create a new user which would allow that user to log into the portal, but that would not allow them to do anything else; to allow them to do something more you need to assign permissions.

There is two ways to assign security and I find the first way to be, by far, the easiest.

Firstly, you can assign security by user (Setup » Users) by selecting the user and then by clicking the toggle next to the role to which you want to assign them:

Continue reading “Implementing Fastpath’s Assure Suite: Assign Permissions”

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

The management of Fastpath Assure is done through the Fastpath Assure portal (in the UK, the address is https://uk.fastpathassure.com/). The administrator account will be configured by Fastpath when the portal is created with additional users being created by that administrator.

To create a new user, log into the portal and open the Users page (Setup » Users). Existing users will be displayed; at the top of the view click the green plus icon to create a new user:

Continue reading “Implementing Fastpath’s Assure Suite: Create new portal user”

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.

As mentioned in a previous post, triggers are created in one company and can be deployed to other companies on the same system, but in a lot of cases, you might need to create them on a development system and then deploy them to the live one.

Fastpath Audit Trails does allow you to do this via the Save Settings function available as a button on the toolbar:

Continue reading “Implementing Fastpath’s Audit Trail: Transfer between systems”