Question
The way we understand it is that any item that is ON the calendar (e.g. meeting, appointment) will have the PR_CLIENT_SUBMIT_TIME set to the date/time of the migration.
However, calendar related items (e.g. Acceptance Notice, Decline Notice, Reschedule Inquiry) will have PR_CLIENT_SUBMIT_TIME set to the "PostedDate" from LN since those have "PostedDate" field/value that is mapped to PR_CLIENT_SUBMIT_TIME? Is that correct?
Answer
Yes, this is correct
We see the following mappings in the message section:
LN.PostedDate = Exchange.PR_CLIENT_SUBMIT_TIME
LN.DeliveredDate = Exchange.PR_MESSAGE_DELIVERY_TIME
Q1: Is this mapping correct and align with what the BT did?
A. If the 'DeliveredDate' field exists, this is correct. If 'DeliveredDate' does not exist, CMTe will use 'PostedDate' for both values.
Q2. Does this mapping apply to both messages received (InBox) as well as messages sent (Sent Items)?
A. Yes Explanation below
For records migrated to Exchange from Notes, Date Sent and Time Sent match Date Received and Time Received, respectively. Those values appear to match the corresponding Lotus Notes record's Received Date/Time. The seconds value for the time also appears to be dropped in the Exchange version.
Example:
Notes
Date Sent: 6/22/2016
Time Sent: 13:07:11
Date Received: 6/22/2016
Time Received: 13:09:16
Exchange:
Date Sent: 6/22/2016
Time Sent: 13:09:00
Date Received: 6/22/2016
Time Received: 13:09:00
Q: Is the mapping the following?
LN.PostedDate = Exchange.PR_CLIENT_SUBMIT_TIME
LN.DeliveredDate = Exchange.PR_MESSAGE_DELIVERY_TIME
OR
are both Exchange fields getting LN.DeliveredDate? Can you explain what is happening here?
A. If DeliveredDate exists, we use it for PR_MESSAGE_DELIVERY_TIME . If DeliveredDate does not exist, we use PostedDate for both values.
Q: Are seconds being truncated for all date/time fields?
A. Yes. The comment in the source code: "notes drops seconds when displaying, OL rounds, so drop seconds here to times match"
This is not a limitation of our product. This is to keep the integrity of the time, so they match in the UI between Notes and Outlook. Outlook rounds the seconds to the nearest minute. If Notes Migrator (CMTe) did not zero out the seconds portion of this field, then Outlook would round the seconds to the nearest minute and could possibly cause a discrepancy with the Sent time, since Outlook only displays hours and minutes.
Example: A Notes message migrates with a time of 12:01:58, the Outlook client would display it as 12:02 if CMTe did not zero out the seconds field.
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center