Skip to main content

EWS - Get Items from 'Draft' folder " This property was requested, but it wasn't returned by the server"

This is a blog post dedicated for people that are working with Exchange Web Server Library (EWS). This is wrapper over EWS API that gives the possibility to a developer to interrogate and communicate with an Exchange Server.
When we are loading the list of emails from a folder we would have the following code:
ExchangeService service = ...
string folderId = ...
ItemView itemView = ...
Folder folder = Folder
  .Bind(service, new FolderId(folderId));
FindItemsResults<Item> items = folder
  .FindItems(searchFilter, itemView);
We get a list of ‘Item’ that we can manipulate by us. It is very easy to extract different email details like ‘Subject’, ‘Id’ or ‘SentDate’.
This solution will works for 99% or the cases, except one. When we want to load the items from ‘Draft’ folder. Surprise, we don’t have the ‘SentDate’ set. Of course this is normal, but EWS library will throw an ugly exception.
Item item = ...
DateTime sentDate = item.DateTimeSent;
What should we do for this case?
Well, the solution is pretty simple. We don’t need to access this property directly, using ‘DateTimeSent’ property. ‘TryGetProperty’ needs to be used in this case. This method give us the possibility to check if a property was set. It is similar with ‘TryParse’. The only difference is that we need to specify what property we want to get.
Each entity type was a XXXSchema class, where all the properties are defined. In our case, to be able to manage this case, we should have the following code:
DateTime sentTime;
bool isSentTimeSet = item
    .TryGetProperty(
      EmailMessageSchema.DateTimeSent,
      out sentTime);
if (isSentTimeSet)
{
  itemHeader.SentDate = sentTime;
}
Enjoy!

Comments

  1. Great article, just what I wanteed to find.

    ReplyDelete

Post a Comment

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine: threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration: TeamCity .NET 4.51 EF 6.0.2 VS2013 It see

Navigating Cloud Strategy after Azure Central US Region Outage

 Looking back, July 19, 2024, was challenging for customers using Microsoft Azure or Windows machines. Two major outages affected customers using CrowdStrike Falcon or Microsoft Azure computation resources in the Central US. These two outages affected many people and put many businesses on pause for a few hours or even days. The overlap of these two issues was a nightmare for travellers. In addition to blue screens in the airport terminals, they could not get additional information from the airport website, airline personnel, or the support line because they were affected by the outage in the Central US region or the CrowdStrike outage.   But what happened in reality? A faulty CrowdStrike update affected Windows computers globally, from airports and healthcare to small businesses, affecting over 8.5m computers. Even if the Falson Sensor software defect was identified and a fix deployed shortly after, the recovery took longer. In parallel with CrowdStrike, Microsoft provided a too