diff options
| author | Denis Ledoux <dle@odoo.com> | 2015-09-01 17:36:52 +0200 |
|---|---|---|
| committer | Denis Ledoux <dle@odoo.com> | 2015-09-01 17:36:52 +0200 |
| commit | 3c0fe940aa5f91a4ed45cf2fa96fb11c079c5733 (patch) | |
| tree | 5b0f551494ec8c3f2b6d6071601a345abc2c1f90 /addons/analytic_user_function | |
| parent | 1c533b193feb7629d87ab1ff740b0cbc7615812e (diff) | |
[FIX] google_calendar: force internal id only on creation
This rev. is related to 1c533b193feb7629d87ab1ff740b0cbc7615812e
The reason why we force the event Google internal id is
explained in the above commit.
Forcing the internal id must be done only when creating the
event in Google, not when updating, for retro-compatibility:
if the event is already in the attendee calendar, with a different
internal id then the other attendee, we must leave it like this,
otherwise Google will be lost.
Diffstat (limited to 'addons/analytic_user_function')
0 files changed, 0 insertions, 0 deletions
