Audit columns

Best practice

Most of the time, audit columns can reuse the same field info. Using "AuditColumns" as field table name is recommended since it is compatible with the guides. Using a single field table for all non-specific audit field info will improve system performance compared to repeating the field info for every field table.
In Grid and InfoSQL it is recommended to use the column name User<suffix> to display the user's name. For example UserInsert instead of UserIdInsert to indicate the column contains the user's name not the UserId.

Audit columns in built-in guides

Create menu item, i.e. "Search, New, Edit, Delete, Detail view"

• If the table contains audit columns, it will create "AuditColumns" field info if it doesn't already exist.
• For the search grid, audit columns will be included.
• For insert/update, audit columns will not be shown, but will be automatically updated.
• For delete, if delete-audit columns exists, the delete menu item will set them instead of deleting the row.

SQL guides

• Will generate JOINs to display full username instead of UserId (grid guides).
• Will add column alias with the correct field name (grid guides).
• Will update audit-columns appropriately (newedit and delete guides).