Whilst this is annoying, I have a work around for this.
Instead of entering multi-day ALL DAY events, enter a _single day_ ALL DAY event and then use the REPEAT option to extend the event for the full duration of your holiday, etc.
This solves the issue and ensures that the ALL DAY event displays correctly in Outlook 2011, ipad and iphone and does NOT colour the entire days
dklondon, thanks for that tip. That certainly does clean up how the events look on the iPhone. I will go ahead and use this method for now, but it *really* clutters up the Outlook and iPad calendars. In week or month view, instead of having a nice long bar spanning the days, it shows the title of the event on each and every day. Not only that, but the repeated title isn't even in the same place each day because single-day events sort higher than multiple day events. So we still really need this to be fixed.
Has anybody found a solution to the problem stated by Karch last year?
I have a similar problem. When I create an all day event in outlook, it does not appear as all-day event in my iphone and as a result the whole day is colored.
This happens with the configuration Outlook server 2010 / iPhone ios 5 and synchronisation between outlook server and iphone over the air.
- Outlook server 2010- "All Day Event" selected. Day n
- iPhone ios 5 - "All-Day" not selected. “Starts” = day n, 12:00am. “Ends” = day n+1, 12:00am
On the other hand, creating all-day event in iphone displaysok in outlook. Does anybody have asolution for this?
I've done a lot of testing with this and thought it would be beneficial to document the results.
- Creating an all-day event in Outlook always seems to get converted into a timed event on the iPhone or iPad
- This can be fixed on an iOS device and as long as that is your only iOS device (or the only one that syncs to Exchange), that fix will "stick", meaning it will display correctly on your iOS device (and in Outlook)
- However, if you have more than one iOS device connected to your Exchange server, such as an iPhone and an iPad, the second device will actually revert the all-day event back to a timed event. If you don't need your work calendar on your iPad you can turn off the calendar sync, fix your all-day events on your iPhone and the fix will "stick"
- Any subsequent changes to the event in Outlook will cause the iOS device to revert it back to a timed event. This happens even if you just add some text to the note or assign a category or virtually any minor thing you do to the event.
- The Outlook event NEVER gets converted to a timed event. It always displays correctly in Outlook as an all-day event. This doesn't necessarily mean that there isn't some bug in Exchange Server, but certainly shows that the issue is really on the iOS side of the equation.
- I thought perhaps the issue was because one of the devices was set to a different timezone or daylight savings or whatever, but that is not the case. I've manually set the same specific timezone on my Mac, iPhone, and iPad (rather than letting it automatically update) and that still doesnt fix the issue.
Apple, please, please, please fix this. It may very well be that this is a bug in Exchange server but Microsoft certainly is never going to fix it and we are all counting on you guys to be able to work around it. Based on the above testing, it sure looks like it is an iOS issue and not an Exchange Server issue.
For further clarification around a proposed fix on Apple's end, consider this example. Let's say that the root cause is an Exchange Server bug where its not setting the all-day event flag on the record that it sends to the iOS device. I have further tested setting the start time to 8am and the end time to 8pm on the timed event on the iOS device and then flipped the switch to make it an all-day event. I have confirmed that regardless of the time, Exchange always returns the event starting and ending at midnight.
So I would suggest that the iOS device simply treat all timed events that start and end at midnight as an all-day event. I'd much rather have it work this way because who's ever going to create a timed event from midnight to midnight? Plus you could always have it start at 12:01am and end at 11:59pm if you wanted your calendar blocked the whole time.
I have the same issue with recurring all day events. Outlook stores these not as an all day event, but rather with an start and end time. When you change them from your apple calendar; it takes two edits to display them properly:
- change to all day event
- change to be for only one day
This bug has not and in all likelihood will not be fixed. Don't blame Apple for this though; this bug is actually a result of the odd manner in which Outlook defines all day events at the code level.
In the iCalendar standard format (which, by the way, is a universally recognized standard, and is not specific to Apple), the officially correct way of defining an all day event is to simply not include any times with the event (i.e. "19991231" instead of "19991231T115959Z").
However, Outlook is wierd and instead defines an all day event with an extra line in the code "X-MICROSOFT-CDO-ALLDAYEVENT:TRUE". Because this is not standard iCalendar format, a lot of calendar viewers don't support it; the officially correct way of dealing with a property that starts with "X-" is to ignore it.
This is a wierd characteristic specific to Outlook, so I would not expect Apple to support it ever. Perhaps it's possible to change the settings of Outlook Server to support proper iCalendar format...
If you're especially curious, here is the official documentation of the iCalendar v1.0 format from the IETF (Internet Engineering Task Force): http://tools.ietf.org/html/rfc2445 (the current version is v2.0, documented here, but the differences are minute)
Hmm, are you saying that all day events created from iPhone appear correctly on the Outlook Server? If they are, that means that Outlook is able to recognize the standard iCalendar format for all-day events, but that it doesn't publish the events in standard iCalendar format. This is a perfectly logical possibility:
When your iPhone sends an event to the Outlook server, it includes a line of code called the PRODID, which, for the iPhone, probably looks something like "-//Apple Inc.//iCal 4.0.2//EN". This basically tells the Outlook Server that the events are going to use the normal iCalendar format for defining all day events, instead of using Outlook's special format. This allows it to correctly add the events as all-day events.
However, PRODIDs only get sent by the sending party, not the receiving party. So when the Outlook Server is sending the events to the iPhone, it has no way of knowing that it is sending to an iPhone, so it just uses the Outlook formatting style. This is where the problem lies - the solution would be to see if Outlook Server allows you configure the formatting it uses when it publishs events.
Not sure of how they have it set up behind the scenes. In trouble shooting, it became clear there was no problem with the calender syncing properly on the iPhone but the issue previosuly described happens with the iPad. If they can get it to work in one place they should also be able to make it functional on the other.