What is the difference between LastModifiedDate and SystemModstamp?

`LastModifiedDate` reflects user and API edits. `SystemModstamp` also advances when the platform itself updates the row, so it is greater than or equal to `LastModifiedDate`.

How far back does the modification history go for cases?

The audit fields hold only the most recent change. For a change history you need Field History Tracking, which is queried from the object's history table.

Can I see what changed, not just that it changed?

Not from these fields. Query the ` History` table for tracked fields, or check Setup Audit Trail for configuration changes.

SOQL Query for Cases Modified Today

SOQL for cases changed today, including LastModifiedBy, audit-field filters, and how to spot integration-driven updates.

Updated 2026-09-09

When something looks wrong in production, the first question is what changed. This query lists today's edits to cases and who made them.

Support orgs generate cases faster than any other object, which makes LIMIT and selective filters mandatory rather than optional.

The query

Cases touched today

SELECT Id, CaseNumber, Subject, LastModifiedDate, LastModifiedBy.Name
FROM Case
WHERE LastModifiedDate = TODAY
ORDER BY LastModifiedDate DESC
LIMIT 200

Narrow to a single user or integration

Integration users show up here in bulk. Filtering by the modifying user separates human edits from automated ones in seconds.

By modifying user

SELECT Id, CaseNumber, Subject, LastModifiedDate
FROM Case
WHERE LastModifiedDate = TODAY
  AND LastModifiedBy.Name = 'Integration User'

Created vs modified

Edits, not creations

SELECT Id, CaseNumber, Subject, LastModifiedDate
FROM Case
WHERE LastModifiedDate = TODAY AND CreatedDate != TODAY

CreatedDate = TODAY - brand-new records only.
LastModifiedDate = TODAY AND CreatedDate != TODAY - edits to existing records only.
SystemModstamp also moves when the platform updates a record, so it is the widest net of the three.

Common mistakes to avoid

Use the API name Case, not the UI label - the two differ on several standard objects.
Wrap literal text values in single quotes; date literals such as LAST_N_DAYS:30 must stay unquoted.
Run the query in a sandbox first if it feeds a bulk update - a WHERE clause that is one character off can select the whole table.
Audit fields are read-only unless Set Audit Fields is enabled, so they cannot be corrected after a bad import.
SystemModstamp changes on platform-driven updates that leave LastModifiedDate alone - use it when hunting integration activity.

Run it faster with TurboKit

Change investigations move between query results, field history, and login history - keeping those in one panel saves the tab juggling.

TurboKit's AI SOQL builder lets you describe the result you want in plain English, returns the query, and exports the rows to CSV or Excel in the same panel - without leaving the Salesforce tab you are already on.

Frequently asked questions

What is the difference between LastModifiedDate and SystemModstamp?: LastModifiedDate reflects user and API edits. SystemModstamp also advances when the platform itself updates the row, so it is greater than or equal to LastModifiedDate.
How far back does the modification history go for cases?: The audit fields hold only the most recent change. For a change history you need Field History Tracking, which is queried from the object's history table.
Can I see what changed, not just that it changed?: Not from these fields. Query the <Object>History table for tracked fields, or check Setup Audit Trail for configuration changes.