Click here to get back home

Best practices for synchronizing custom properties of PocketOulook.PimItem

 HomeNewsGroups | Search | About
 microsoft.public.pocketpc.activesync    Post an article   get this group's latest topics as an RSS feed add this group's latest topics to your My MSN content add this group's latest topics to your My Yahoo content
Subject Author Date
Best practices for synchronizing custom properties of PocketOulook.PimItem Joris van Lier 02-20-2008
Posted by Joris van Lier on February 20, 2008, 4:24 am
Please log in for more thread options
I'm working on a managed (C#) Windows Mobile 5.0 Application that
manipulates Custom Properties of PimItem (Appointment) objects.

Problem:
It seems that neither Outlook User Properties nor PocketOutlook custom
properties are synchronized to the Exchange 2003 Server by ActiveSync

Work-around:
My current work-around serializes the custom properties into the PimItem
(Appointment) body,
although this method works, it's not aesthetically pleasing for our desktop
users because a blob of XML is visible when these appointments are viewed in
outlook, additionally it may make the application more susceptible to
user-error's because of the possibility of unintentionally editing the XML
blob in the body of the appointment.

Question:
What are best practices for:
1. saving "Custom Properties" to a PocketOutlook PimItem
2. having these properties propagated by ActiveSync to an Exchange Server
3. accessing such properties from a managed Desktop application, or Exchange
Store Sink


Joris van Lier


Posted by Chris De Herrera on February 21, 2008, 11:44 pm
Please log in for more thread options
Hi,
Unfortunately, there is no support to sync custom properties or custom
fields with Exchange ActiveSync or ActiveSync on your PC. The workaround
you are using is the best one I have heard of.


--
Chris De Herrera
http://www.pocketpcfaq.com
http://www.pocketpctalk.com
http://www.tabletpctalk.com
http://www.mobilitytalk.com

> I'm working on a managed (C#) Windows Mobile 5.0 Application that
> manipulates Custom Properties of PimItem (Appointment) objects.
>
> Problem:
> It seems that neither Outlook User Properties nor PocketOutlook custom
> properties are synchronized to the Exchange 2003 Server by ActiveSync
>
> Work-around:
> My current work-around serializes the custom properties into the PimItem
> (Appointment) body,
> although this method works, it's not aesthetically pleasing for our
> desktop users because a blob of XML is visible when these appointments are
> viewed in outlook, additionally it may make the application more
> susceptible to user-error's because of the possibility of unintentionally
> editing the XML blob in the body of the appointment.
>
> Question:
> What are best practices for:
> 1. saving "Custom Properties" to a PocketOutlook PimItem
> 2. having these properties propagated by ActiveSync to an Exchange Server
> 3. accessing such properties from a managed Desktop application, or
> Exchange Store Sink
>
>
> Joris van Lier


Similar ThreadsPosted
Unable to send custom properties (of appointment item) between poc January 30, 2007, 2:54 am
Pocket Outlook Contact Custom Properties and Active Sync October 4, 2006, 4:27 pm
Q: ActiveSync and "named properties" August 27, 2006, 9:22 pm
Syncing Custom Fields November 22, 2005, 9:43 pm
Modify Custom Dictionary August 7, 2006, 7:14 pm
custom port number October 17, 2006, 8:04 am
Outlook Custom Fields sync? August 3, 2008, 7:07 pm
ActiveSync Service Provider for custom contacts May 9, 2007, 10:34 am
ActiveSync does not allow custom sync settings with Windows Mobile March 16, 2006, 9:00 am
Need help with SMS Synchronizing June 16, 2005, 11:52 am

Our other projects:

Art Dolls, Fairies and Mermaids - Sunnyfaces.net

Roy's Linux, Programming and Search Engines messages

1-Script XML SitemapXML Sitemap