Ignite Global Support Home Start a conversation Sign in
Start a conversation
  1. DNN Corp. Customer Support
  2. DNN Articles
  3. Articles

DNN Evoq v9.13.3: Why Most Files May Show the Same <code>LastModifiedByUserID</code> (Expected Behavior)

Contents

Overview

In DNN Evoq (for example, v9.13.3), it is possible to see most rows in [dbo].[Files] showing the same value for LastModifiedByUserID (for example, “96% of files are stamped with <user_id>”). This can occur even if the administrator did not intentionally “edit” individual files, because DNN updates file metadata during indirect file/folder operations such as move/rename/permission changes and folder refresh/sync/reconciliation—especially after filesystem-level changes like a server migration.

<supportagent>

Agent Notes

Investigation Summary:

Reviewed how DNN Evoq updates file metadata and what actions can change [dbo].[Files].[LastModifiedByUserID]. Validated that Site Administrators (not only Superusers) can execute file/folder operations that update file/folder records. Performed controlled tests to observe when bulk metadata updates occur (including scenarios involving filesystem changes followed by sync/reconciliation).

Findings:

  • Site Administrators can perform operations that update file/folder metadata, which can stamp many records with their user ID.
  • A simple “sync” may not always reproduce changes in every scenario, but disruptive filesystem change + sync/reconciliation can update LastModifiedByUserID in bulk.
  • After temporarily removing and reintroducing assets at the filesystem level and running sync actions, LastModifiedByUserID changes were observed; other metadata (for example CreatedOnDate) may also change depending on whether DNN treats items as reintroduced/recreated.
  • The behavior is consistent with intended DNN metadata handling after filesystem-level changes (for example, copying files during a server migration and then running a root refresh/sync).
  • Audit validation can be performed via Admin Logs and/or querying EventLog for LogUserID = <user_id>.

Escalation: None

In the observed scenario, a likely real-world trigger was a server migration (filesystem copy) followed by an Asset Manager/File Manager root refresh. Historical restoration was not feasible due to lack of old backups.

</supportagent>

Key Information

  • LastModifiedByUserID can be updated by indirect actions that change file/folder metadata (not only by editing file contents).
  • Common actions that update file/folder metadata include:
    • Moving or renaming files/folders
    • Folder-level permission changes that touch file/folder records
    • Asset Manager / File Manager folder refresh/sync/reconciliation actions
  • This is especially common after a server migration where files are copied at the filesystem level and then a root refresh/sync is run to reconcile DNN’s database with the filesystem.
  • To confirm what DNN recorded for the user ID stamped on files, review Admin Logs for file/folder events and/or query EventLog for that user.

Customer Impact

No corrective action is required if the updates align with expected administrative activity (for example, post-migration sync/reconciliation, bulk moves/renames, or permission changes).

If you need an audit trail, use Admin Logs and/or the EventLog table to correlate file timestamps (for example, LastModifiedOnDate) with recorded events. If stamping continues without matching log evidence, collect examples (file IDs, timestamps, and event output) for deeper review.

Frequently Asked Questions

1. Is this limited to Superusers?

No. Site Administrators can also perform operations (move/rename/refresh/sync/permissions) that update file metadata and therefore update LastModifiedByUserID.

2. What kinds of actions can update LastModifiedByUserID even if I didn’t “edit” a file?

Bulk or indirect operations such as folder/file move/rename, permission changes, and Asset Manager/File Manager folder refresh/sync/reconciliation actions can update file metadata.

3. How do I quickly see what DNN recorded for the user ID stamped on the files?

Query the event log table and review Admin Logs around the affected dates.

EventLog query:

SELECT *
FROM EventLog
WHERE LogUserID = <user_id>;

Admin Logs (UI): Filter for file/folder events such as created, deleted, updated, and moved, and narrow the timeframe to when you first see the shift in LastModifiedOnDate.

4. We migrated servers by copying files. Can that contribute to this?

Yes. Files copied/changed at the filesystem level often require a refresh/sync/reconciliation step in DNN. The user who runs that step can become the LastModifiedByUserID for many file records.

5. When should this be escalated?

If metadata changes occur but there are no matching Admin Log or EventLog entries, or you can reproduce unexpected bulk stamping without any file/folder operations that should touch metadata, further review is needed. When requesting deeper review, provide DNN version/build, example affected FileId values and timestamps, relevant EventLog output for the timeframe, and details of any migration/sync/automation activity.

Choose files or drag and drop files
ai_initiated
atlas_studio
kb_automation
Was this article helpful?
Yes
No

  1. Priyanka Bhotika

  2. Posted

Comments