Skip to main content
Configuration

How custom event receivers affect OnePlaceMail upload process

Article describes inconsistent upload issues and ways of fixing them.

Issue

Library event receivers may affect the OnePlaceMail uploading process resulting in inconsistent errors.

 

Scenario 1

File has been modified error. There could be several problematic emails in the upload results window, but some of them are uploaded successfully:

01 file has been modified

 

 

Scenario 2

Metadata was not populated. Some of the email messages left without email properties updated after uploading several emails:

02 metadata not populated

 

 

Reason

OnePlaceMail uploads an email message in several steps and some of them include the following events:

  1. ItemAdding - when msg or other file type is uploaded into library this event is triggered - occurs before added
  2. ItemAdded - when msg or other file type is uploaded into library this event is triggered - occurs after added
  3. ItemUpdating - we get the item again in library and apply the metadata to item so this event is triggered - occurs before metadata applied
  4. ItemUpdated - we get the item again in library and apply the metadata to item so this event is triggered - occurs after metadata applied

Any custom code written in these event handlers could cause an issue.

Library event receivers have one of the two synchronization types either Asynchronous or Synchronous.

Asynchronous event receivers are executed after committing the file to the database, thus it could happen before 3rd step of OnePlaceMail process (which leads to the error "The file has been modified"

Schedule a demo

See the OnePlace Solutions product suite in action and unlock the potential of your data by leveraging the SharePoint platform.

Try free

Download and try the full OnePlace Solutions product suite for Windows Desktop and Apps for Microsoft 365.

Contact us

We're here to help, so please don’t hesitate to get touch with any questions you may have.