PROBLEM

The Dataverse does not record milliseconds in its date/time columns.

We have various jobs in our source systems (not all under our own control) that produce changes in short periods of time.

In Dynamics we have plugins that attempt to locate and set the "current state" of various entities based on the LAST action taken.

IMPACT

Without milliseconds being available, some entities are set to the wrong "current state" because the code randomly selects one record from the set of records falling in the last second of activity as the entity's "last action".

This can have potentially legal ramifications.

SOLUTION

ALL columns in Dataverse need to support milliseconds.

This includes built-in columns (e.g.: createdon, modifiedon) as well as custom columns.