Some updates:
1) We had the check-in and check-out times reversed (sorry!), but this has now been corrected. (I don't think this would have affected FlipKey integration, see below.)
2) We are now also using the check-in & check-out times you have entered in your Property Setup. To support this, we have beefed up the restrictions on the allowed values for entering times in the check-in & check-out times. It will support either "4:30 PM", or "16:30" (European/Military) formats.
3) The iCal export is not yet using any custom check-in/check-out fields you may have defined for each booking. Our plan is to next update the Booking Details page so that you can override the check-in & check-out times for each booking (without resorting to custom fields), and these new fields will have the same format requirements. By getting a little stricter with these, we can reliably parse them and this makes them available to the iCal export.
4) Because these check-in & check-out times were "free-text" entry fields for years prior, we had to go through the database and "correct" any times that did not fit the format. For example, some of you had times like "12 noon", so we had to convert these to "12:00 PM". We apologize for any inconvenience this may have, but it's for the greater good!
5) Our sense, based on feedback from members, is that FlipKey is automatically "trimming" the last day off of imported Bookerville bookings, in order to jive with their own calendar format, which really only blocks dates in which guests are staying that night.
Because of this, for a booking that runs from July 20 - July 27:
Bookerville will show July 20th partially blocked (the latter-half of the day), and July 27th partially blocked (the earlier half of the day) FlipKey will show the whole day blocked for July 20th, but the whole day of July 27th will be open.
It's unfortunate that FlipKey's calendars are so simplified like that, but that's how they're running them right now. The good news is that they appear to recognize this incompatibility and have proactively taken steps to deal with it.
That's all for now - please do report back what you experience; we thrive on our member feedback.
Thank you,
John
|
|
|