I have this problem where if I create a Calendar Entry on my PDA and set the Status to Free, when it syncs it changes to Tentative on my phone. Now if I change it from Tentative to Free, it leaves it alone. Has anyone else seen this? Here is the instructions to replicate it:Steps to reproduce.
Create Calendar entry on PDA
Set Status to Free
Sync
Traveler will set the entry’s status to Tentative
Set Entry back to Free
Sync
Traveler will leave it alone this time…
Subject: Mapping WM time states to Domino state
This is caused by a difference in the states that WM and Domion support.
WM: Busy, Tentative, Free, and Out of Office.
Domino: Avaliable and Unavaliable.
WM Tentative and Free are mapped to the same thing on the Domino server: Available.
When data flows from the server to the device, Available is mapped to Tentative.
When an entry is created in WM and sent to Domino (during the sync), it does not have all the Domino fields completed. As part of the sync, the Domino fields are completed and sent to the device so that the device now has the complete entry too. When this data is sent to WM, the Available gets mapped to Tentative and you see it as Tentative on the device. On subsequent syncs, the Domino information is already filled in, so the server just accepts the update from the device and does NOT send back a change to update anything. Thus, for syncs after the first one with changes on the device, the mapping from Available to Tentative does not have to be applied again (but it will always show up as Available on the Domino side). If the change was made on the Domino side, then you would see the device have Tentative again.
For the sake of this description, the Domino side includes the Notes client because that is how you would change the data on the Domino side.
Subject: Future Fix?
So do you know if they might change this behavior in a future release of Traveler? Meaning that if I set it to Free that it will stick unless I manually change it.
Subject: Fix for WM Free to Available mapping?
There is no plan to change the behavior.
If you come up with a strong use case for changing it, that might help. But remember, the focus/mentality is that the Domino data is the ruler and we try to map that as best we can to the data opens on the devices; thus, we are less concerned with keeping things that a device can do (but Domino does not) intact because there are too many devices that all do something slightly different or offer additional features.
Said another way, the focus is on Domino users who want to use WM and not WM users who want to use Domino. I know that sounds a little harsh, but we are Notes/Domino after all.