Skip to main content

Appointment label Colour Changing Event Sink

[2/2/2005 updated this post and script to use named property instead the custom Mapi prop]

One of the cool features that was implemented in Outlook 2002 was the ability to change the colour of appointment labels to help distinguish between different types of appointments. (see http://www.slipstick.com/calendar/colorcal.htm for a good description of this feature). But because of the laziness factor I find that I rarely use this feature because I usually forget to set it. One of the things that I really wanted this to do also was be able to show me at a glace which meetings in my calendar where internal meeting (only contained internal attendees) and which meeting contained external attendees (this can be usefull in the morning). Putting this into an event sink turned out to be a really easy solution. All I needed was some code that would go though the attendees collection of a appointment object when the appointment was created and check each of the address's of the attendees to see if they where local address's or external. I leaned on the side of low tech and just decided to go for a match against one local domain. The property that controls the appointment colour is http://schemas.microsoft.com/mapi/id/{00062002-0000-0000-C000-000000000046}/0x8214 and there are 10 integers (data type needs to be long) you can pass to it representing the different colours available in Outlook. I decided to go for blue for external meeting and green for internal meeting. The other check the code performs is to check the number of attendees in the appointment this is because I only wanted it to work on meeting or appointments where someone else other then me was attending. NOTE: I’ve restricted this sink so it only takes action on newly created appointments this is because a sink that updates properties on an existing message can be pretty dangerous. If you look at the logic when the sink fires it updates properties on the message and saves that message which then causes the sink to fire again and again and before you know it your transaction logs are full and the store is dismounted (Doh!)

The appointment label text provides a bit more of a challenge its located in the http://schemas.microsoft.com/mapi/proptag/0x36DC0102 property in an undocumented binary form, although on first look it doesn’t appear that daunting it looks like its just in byte format padded with a few zeros but this is a challenge for another day.
The code for the sink looks like this, Ive posted a copy up here


<SCRIPT LANGUAGE="VBScript">

Sub ExStoreEvents_OnSave(pEventInfo, bstrURLItem, lFlags)

Const EVT_NEW_ITEM = 1
Const EVT_IS_DELIVERED = 8

If (lFlags And EVT_IS_DELIVERED) Or (lFlags And EVT_NEW_ITEM) Then

chgappt = 0
LocalSearchdomain = "@yourdomain.com"
set apptobj = createobject("CDO.Appointment")
apptobj.datasource.open bstrURLItem,,3
cval = apptobj.fields("http://schemas.microsoft.com/mapi/id/{00062002-0000-0000-C000-000000000046}/0x8214")
if apptobj.Attendees.count > 1 then
for each attend in apptobj.Attendees
if instr(lcase(attend.address),LocalSearchdomain) = 0 then
chgappt = 1
end if
next
if chgappt = 1 then
if cavl <> 2 then
apptobj.fields("http://schemas.microsoft.com/mapi/id/{00062002-0000-0000-C000-000000000046}/0x8214") = clng(2)
apptobj.fields.update
apptobj.datasource.save
end if
else
if cavl <> 3 then
apptobj.fields("http://schemas.microsoft.com/mapi/id/{00062002-0000-0000-C000-000000000046}/0x8214") = clng(3)
apptobj.fields.update
apptobj.datasource.save
end if
end if
end if
apptobj = nothing

end if

End Sub

</SCRIPT>

Popular posts from this blog

Exporting and Uploading Mailbox Items using Exchange Web Services using the new ExportItems and UploadItems operations in Exchange 2010 SP1

Two new EWS Operations ExportItems and UploadItems where introduced in Exchange 2010 SP1 that allowed you to do a number of useful things that where previously not possible using Exchange Web Services. Any object that Exchange stores is basically a collection of properties for example a message object is a collection of Message properties, Recipient properties and Attachment properties with a few meta properties that describe the underlying storage thrown in. Normally when using EWS you can access these properties in a number of a ways eg one example is using the strongly type objects such as emailmessage that presents the underlying properties in an intuitive way that's easy to use. Another way is using Extended Properties to access the underlying properties directly. However previously in EWS there was no method to access every property of a message hence there is no way to export or import an item and maintain full fidelity of every property on that item (you could export the...
Read more

The MailboxConcurrency limit and using Batching in the Microsoft Graph API

If your getting an error such as Application is over its MailboxConcurrency limit while using the Microsoft Graph API this post may help you understand why. Background   The Mailbox  concurrency limit when your using the Graph API is 4 as per https://docs.microsoft.com/en-us/graph/throttling#outlook-service-limits . This is evaluated for each app ID and mailbox combination so this means you can have different apps running under the same credentials and the poor behavior of one won't cause the other to be throttled. If you compared that to EWS you could have up to 27 concurrent connections but they are shared across all apps on a first come first served basis. Batching Batching in the Graph API is a way of combining multiple requests into a single HTTP request. Batching in the Exchange Mail API's EWS and MAPI has been around for a long time and its common, for email Apps to process large numbers of smaller items for a variety of reasons.  Batching in the Gr...
Read more

EWS-FAI Module for browsing and updating Exchange Folder Associated Items from PowerShell

Folder Associated Items are hidden Items in Exchange Mailbox folders that are commonly used to hold configuration settings for various Mailbox Clients and services that use Mailboxes. Some common examples of FAI's are Categories,OWA Signatures and WorkHours there is some more detailed documentation in the https://msdn.microsoft.com/en-us/library/cc463899(v=exchg.80).aspx protocol document. In EWS these configuration items can be accessed via the UserConfiguration operation https://msdn.microsoft.com/en-us/library/office/dd899439(v=exchg.150).aspx which will give you access to either the RoamingDictionary, XMLStream or BinaryStream data properties that holds the configuration depending on what type of FAI data is being stored. I've written a number of scripts over the years that target particular FAI's (eg this one that reads the workhours  http://gsexdev.blogspot.com.au/2015/11/finding-timezone-being-used-in-mailbox.html is a good example ) but I didn't have a gene...
Read more
All sample scripts and source code is provided by for illustrative purposes only. All examples are untested in different environments and therefore, I cannot guarantee or imply reliability, serviceability, or function of these programs.

All code contained herein is provided to you "AS IS" without any warranties of any kind. The implied warranties of non-infringement, merchantability and fitness for a particular purpose are expressly disclaimed.