Return
-
Title
Migrated reservations missing Exchange PidLidGlobalObjectId. -
Description
Some migrated reservations are missing Exchange PidLidGlobalObjectId
-
Cause
Resource reservations created by an Exchange organizer through the CMN mail connectorare not migrated properly if the exception list containing Subject.When a recurring meeting has an instance that doesn't follow the definedrecurrence rule, an exception attachment is added.When MNE processes the recurrence rule for the meetings, it will checkthe exception attachment for Subject, Location, AlarmSet among other fields.If the instance's exception Subject line exists and is different fromthe series Subject line, it will overwrite it with the exception Subject line. -
Resolution
RESOLUTION:
This has been identified as a product defect that will be addressed in next release.
The Product Defect number is TFS# 704915:Resource reservations created by an Exchange organiserthrough the CMN mail connector are not migrated properly if the exception listcontaining SubjectWORKAROUND:Notes: These parameters might not work though in some scenarios.Also they are not documented at the moment.- For scheduled events originated from Notes, the following parameter will setthe UseMapiOwnerApptId property to the owner appointment id.[Exchange]UseMapiOwnerApptId=1- For scheduled events originated from Exchange, the following flag instructs MNE to process appointment headerand set the PidLidGlobalObjectId.[Exchange]LookupOwnerApptId=1The parameters UseMapiOwnerApptId, and LookupOwnerApptId are basedon a flag read from Notes document