Mapping Date and Time Fields for Produced Data Imports

Follow

Mapping Date/Time Metadata Fields in Load Files

If your production's load file contains metadata fields with date/time information, it is important to ensure these values are mapped correctly for accurate metadata loading.

The following fields have specific date/time formatting requirements:

  • Email Sent
  • Email Received
  • Created Date Time
  • Modified Date Time
  • Last Print Time

There are two scenarios to consider when mapping these fields:


Scenario 1: Combined Date and Time in One Column

If the values are in a single column formatted as:

  • mm/dd/yyyy hh:mm
  • mm/dd/yyyy hh:mm:ss
  • mm/dd/yyyy hh:mm AM/PM
  • mm/dd/yyyy hh:mm:ss AM/PM

Then map directly to:

  • Email Sent
  • Email Received
  • Created Date Time
  • Modified Date Time
  • Last Print Time

Scenario 2: Date and Time in Separate Columns

If the values are split into two columns:

  • one for the date:mm/dd/yyyy 
  • one for the time:
    • hh:mm
    • hh:mm:ssh
    • h:mm AM/PM
    • hh:mm:ss AM/PM

Then map the following field pairs:

  • Email Sent DateEmail Sent Time
  • Email Received DateEmail Received Time
  • Created Date Time DateCreated Date Time Time
  • Modified Date Time DateModified Date Time Time
  • Last Print DateLast Print Time

Proper mapping ensures accurate processing and display of metadata during review and production.

0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.

Articles in this section

See more