• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 550
  • Last Modified:

FM - Auditing Feature?

Boss wants an auditing trail in Filemaker.  A one step history is easy with the auto enter modification data and account name, but he would like to keep track for several changes.  How would you do that?  Would you create a series of set fields and copy field4 to field5, then field3 to field4 and so on?
0
rvfowler2
Asked:
rvfowler2
  • 4
  • 4
2 Solutions
 
Will LovingPresidentCommented:
I've used Nightwing's SuperLog Audit System (in various incarnations) with great success. It's been extremely helpful. The only issue I've encountered with it is if you have a very large number of fields marked for auditing, it can significantly slow down imports.

http://www.nightwing.com.au/FileMaker/demos8/demo809.html
0
 
rvfowler2Author Commented:
Looks interesteing, but they provide no instructions whatsoever.  Assuming you install this on the server and that it is an AddOn, but some instructions would be nice.
0
 
Will LovingPresidentCommented:
It's really very straightforward. You simply import the three Custom Functions: SuperLog, ScriptLog and PrepLog. Then you add an Audit field (they call it "Data_Log") to each table that you want to track and populate the Auto-Enter Calculation with the SuperLog () function and any fields you want to be tracking.

To display the results, I usually create a separate layout with just the Data_Log field on it and a "Close" button. The user displays the layout via a script linked to either a button or a menu item. You can just copy the field from the demo if you want. Be aware that the nice column spacing in the demo is achieved by applying tab formatting to the field.
0
Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
rvfowler2Author Commented:
I'll test it.  The only problem if I understand this correctly is that it tracks per field when we are really interesed in any change someone makes on the record, though I suppose we could emphasize key fields that a mistake in which would cause the most problems.
0
 
Will LovingPresidentCommented:
You can list as few or as many fields as you want. Many fields are not likely to require monitoring, but you might be able to modify the Custom Function to monitor for any change in the record. Probably easier though to just specify the key data fields.
0
 
rvfowler2Author Commented:
Also, the auto-enter text is as follows.  Do I have to create a 2nd repetition for each field or is TheText[2] simply an example of a second field you would use?

SuperLog ( Data_log ; TheText & TheText[2] & TheNumber & TheDate & TheTime )
0
 
Will LovingPresidentCommented:
TheText is a repeating field; in the Demo it's used for First and Last name. In the Auto-Enter calculation TheText traps for changes to the first repetition, TheText[2] traps for changes to the second repetition of the field.
0
 
rvfowler2Author Commented:
Thanks, Wll.  Works well in testing.  Notice that it shows results per record.  Tried using an X relationshi and putting it in a Footer or Grand Trailing Summary, but wouldn't show results.
0

Featured Post

The 14th Annual Expert Award Winners

The results are in! Meet the top members of our 2017 Expert Awards. Congratulations to all who qualified!

  • 4
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now