Skip to main content

Very often when we’re investigating why this record or row was created, in some cases it help if you can go directly to that individual. Maintenix database keeps in most of it’s tables fields like CREATION_DT (Creation Date), REVISION_DT (Revision Date) and REVISION_USER, but it’s missing the CREATION_USER.

In some areas if we’re lucky and Creation Date and Revision Date matches, then we know the user who created that row in the database, if not we’re kept in the dark.

Is it hard for IFS to add this field to majority of it’s table where end user is able to create an entry, like Locations etc.

Hi Bjarki,

This wouldn’t be difficult per se. These columns are managed via database triggers, and therefore the implementation and maintenance of such a solution can be deployed without any effect to Maintenix itself.

Each of the desired tables would have to have a column added. Do you have a discrete list of tables where you believe this information would be more valuable?

For custom solutions, a new after insert trigger could be designed to copy the revision_user into the creation_user column. Were IFS to deploy a solution like this, we would more likely edit the existing MX_TRIGGER.before_insert function to perform the copy.

The main detractor would be the increased data size, and the performance penalty associated with a new trigger.

This request is more suitable for the Ideas area of the portal. Shall I move the ticket?

Reply


Terms & ConditionsCookie settings