|
|
 |
Recent Update
|
 |
| |
LATEST RELEASE:
>> v2.1.29.0 <<
|
|
|
|
note: If you have any problems installing
gSyncit try clearing your browser cache and download gSyncit to your
desktop first. Then install gSyncit from your desktop.
If you are using a 64-bit version of Windows and NOT
using Outlook 2010 64-bit then please install the
32-bit version of gSyncit. You need to install the
appropriate 32/64 bit version of gSyncit based on the
32/64 version of Outlook you are using.
time zone functionality: If using Outlook 2003
you may need to update your time zone information to the
most current Windows time zone settings. Please install
and follow the instructions the
Microsoft Time Zone
Update
to make sure that your time zone information can be
mapped correctly between Outlook and Google. |
Update History / Release Notes
|
 |
gSyncit v2.x updates are free
for those that purchased licenses on or after January 1st,
2009 USA/Pacific Time. gSyncit licenses purchased prior to this
date require the
purchase of v2.0 upgrade licenses at a discounted
price. When upgrading you will be prompted to provide your original
license key. Read more about what's new in v2.0
here.
gSyncit v1.x is no longer be supported after March 2010.
Update History / Release Notes
|
 |
v2.1.29.0 - July 2010
|
|
 |
-
FIX:
Corrected issue with the notes sync where the subject of the
Outlook note would get duplicated when updated from a Google
document.
-
FIX: Corrected error "This property cannot be changed
for a single instance of a recurring meeting." when gSyncit
incorrectly attempts to assign a category to a recurring
event exception which is not supported by Outlook.
-
FIX: Corrected issue with the settings import/export
functionality where the export would create a .dat file
while the import would look for a .xml file. The
import/export process will use a settings.dat file format.
-
UPDATE:
Added option to control how gSyncit handles events that were
previously synced using a day range and now occur outside the current sync
range when syncing by x days back/forward.
By default gSyncit will NOT delete items that occur outside
the specified day range as the date moves forward each day.
It will only delete items that were deleted by the user
which occur within the active date range set as a result of
using the day range settings.
A new configuration option has been exposed that allows any
previously synced items that occur outside the current sync
day range to be deleted from the target calendar.
This configuration option is available as the global sync
options level and per each calendar mapping.


-
UPDATE:
Added option to use Gmail's structured address format. This
option was added to allow for proper address formatting when
syncing with the iPhone/iTouch. This option is off by
default.

v2.1.26.2 - June 2010
|
|
 |
- FIX: Corrected
minor issue where opened Outlook events are automatically
closed when updated during the sync process.
- FIX: Updated the
notes sync process to only read documents that are flagged
as document. This prevents non-document entries from
updating to the Outlook notes folder.
- FIX: Corrected
issue selecting a Google calendar when not using a @gmail.com
username. Users would receive an invalid credentials error
when attempting to select a Google calendar despite validating
credentials working properly. This fix allows users with
usernames like me@hostname.com to use gSyncit to access
their calendars.
v2.1.25.1 - June 2010
|
|
 |
-
FIX: Corrected critical issue introduced
in the v2.1.24 release where user defined sync
date ranges for calendar mappings were not
properly saved when updating the calendar
mapping. The calendar sync range would revert
back to the default sync date range.
v2.1.24.2 - June 2010 |
|
 |
-
FIX: (TIME ZONE FIX) Corrected incorrect start/end time issue
when synchronizing recurring events in a
different time zone other than the default
Windows and Google calendar time zone.
gSyncit will now properly sync Outlook
_recurring_ events, that occur in a different
time zone, with a Google calendar event. gSyncit
will also now correctly update Outlook event
time zone information with the recurring event
time zone information allowing the Outlook
calendar to properly display event date/time
information based on the current windows time
zone.
-
FIX: (DAYLIGHT SAVINGS FIX) Resolved time zone shifting issue related to
syncing recurring events in other time zones
with different DST start/end times. gSyncit
failed to include the VTIMEZONE information with
recurring events. This caused recurring events
in other time zones to fail to render
incorrectly
on the Google calendar when crossing DST
boundaries.
-
FIX: Corrected issue where when a product
update is available multiple update
notifications will appear when using the
automatic sync option.
-
FIX: Corrected minor issue related to
recurring events having the all-day flag being
set for non all-day events. This caused a sync issue when syncing
from events from Google to Outlook to Exchange
and then finally to the Motorola Droid.
-
FIX: Corrected issue setting the time
zone when syncing recurring events from Outlook
to Google using the option to sync minimal data.
In the v2.1.21 release this issue produces a 400
error while writing to the Google calendar when using
the option to sync free/busy information.
-
FIX: Corrected issue where when deleting
a recurring item that occurs within the sync
date range but _starts_ outside of the range
then then deleted item gets restored during the
sync.
-
FIX: Corrected issue where changes to
task properties in the Google event description
incorrectly required a space between the
property name and its value. For example, "Importance:high"
would not sync when a space was missing after
the ":".
-
FIX: Corrected "The recurrence pattern is
not valid." error when updating an Outlook event
where the source recurrence value contains an
INSTANCE value for yearly recurring events.
-
FIX: Corrected known issue where if
an Outlook event is opened during the sync
process and the opened event is later is saved
then it will get converted to a weekly recurring
event by Outlook. This appears to be a bug
within Outlook which is triggered by calling
GetRecurrencePattern() rather than using
IsRecurring on the appointment to determine if
an event is recurring.
-
FIX/UPDATE: Restored the global calendar
sync range configuration after a number of users
were not pleased with its removal from the
product in the v2.1.21 release.

-
FIX: Resolved duplicate contact creation
issue when using the FileAs value for the Google
full name that also contains company
information. When gSyncit matches existing Gmail
contacts with existing Outlook contacts if the
FileAs name contains company information then
gSyncit would fail to match the contact records
causing a duplicate to be created. The matching
logic has been further improved to support
proper matching when using the FileAs value for
the Gmail contact name value.
-
UPDATE: Changed the default task sync
option to enabled for the option to sync task
properties in the Google event description. In
prior versions users had to explicitly set this
option.

-
FIX: Added configuration option to turn
on/off send attendee notifications when
inserting/updating Google events. This option is
turned _off_ by default.

-
UPDATE: Revised the delete dialog to note
the target where items are going to be deleted
from.
-
UPDATE: Revised logic for extracting
email addresses from Outlook meeting event
attendee's and populating the Google event
participant list.
-
UPDATE: Updated the calendar keyword
filtering functionality to include the event
location field.
-
UPDATE: Updated the sync by day range to
not delete items that fall outside the date
range as the day range shifts forward each day.
-
UPDATE: Added the ability to only assign
categories to new events imported from the
Google calendar and not perform any filtering
based on category assignment.

-
UPDATE: Added support for setting and
displaying the task priority on Google events
within the event location field. The Google
event location will show as High, Low, or
Normal.
v2.1.21 - May 2010
|
|
 |
v2.1.20.4 - May 2010
|
|
 |
-
FIX: Corrected "too
many items" issue with the delete
confirmation dialog a large number of items are deleted.
-
FIX: Corrected issue with the calendar
category filter feature where when the option
"Don't filter by category" is selected but categories are still defined in the category
list then those categories would incorrect get
assigned to Outlook events.
-
FIX: Corrected "The recurrence pattern
is not valid." when updating recurring event day
of week mask in the Outlook calendar for certain
recurring event patterns (e.g. first day of
every month). This error produced a more
specific error of...
Error Details:
at
Microsoft.Office.Interop.Outlook.RecurrencePattern.set_DayOfWeekMask(OlDaysOfWeek
DayOfWeekMask)
-
FIX: Corrected issue where the
licensing terms were not properly appearing on
the About panel of the settings dialog in the
64-bit version of gSyncit.
-
FIX: Added fix for Outlook 'Cannot
Save Item' item. This error occurs when gSyncit
attempts to update a cancelled Outlook
appointment. Once the status of a Outlook event
is marked as cancelled any updates are rejected
to the Outlook event.
-
FIX: Added a fix for Outlook events
randomly changing from a single event to a
recurring weekly event. If an Outlook event is
opened during the sync process then it is closed
and synchronized. When the event is opened again
in Outlook or modified within Outlook then
_OUTLOOK_ switches the event to a weekly
repeating event. A workaround has been
implemented but this obviously appears to be a
defect with Outlook.
-
FIX: Corrected 'DisplayType' failure when attempting to determine an appointment attended type. This error indicates that Outlook was unable to access the display type information for the attendee. When this happens gSyncit is unable to determine the type and email address of the attendee and skips over the entry.
The common error associated with this issue is "An
object could not be found ...
Microsoft.Office.Interop.Outlook.Recipient.get_DisplayType()"
-
FIX:
Corrected issue where gSyncit still prompted
user to confirm deletes for recurring event
exceptions when the option to manually confirm
deletes is disabled.
-
UPDATE:
Updated the 64-bit installer so
that it installs gSyncit into the "Program
Files" folder instead of the "Program Files
(x86)" folder.
-
UPDATE: Removed the default calendar
sync options from the settings dialog. These
options are not exclusively set on the calendar
mapping tab. This was removed to resolve some
confusion between the default calendar sync date
range and those available on the calendar
mapping. The default settings are automatically
migrated to the calendar mapping as needed to
avoid having to reconfigure any sync date
ranges.
-
UPDATE: Added new Outlook Toolbar item
to sync individual item types. A number of users
have requested a way to sync individual item
groupings rather than have to constantly sync
items as part of the auto sync process.

-
UPDATE: Added option to bypass any
proxy settings including using the windows
automatic proxy detection logic.

-
UPDATE:
Changed the reminder logic to explicitly use the
popup reminder time for Outlook events when
multiple reminders are defined for a Google
calendar event.
|
v2.1.17.0 - May 2010
|
|
 |
-
FIX: Corrected issue with photo sync
process where when a Outlook contact contains a
specific attachment type causes a failure syncing the contact photo
to Gmail.
-
FIX: Corrected issue with Outlook
contact photo image scaling when
transferred to the Gmail contact. This scaling
logic is no longer required by Gmail.
v2.1.16.0 - May 2010
|
|
 |
-
FIX: Corrected issue with the
enable/disable check boxes for mappings not
being saved when the settings dialog is closed.

-
FEATURE: Sync Outlook tasks with
Google events using the reminder date/time!
Added option that allows
syncing the Outlook task reminder date with a
Google event start date/time.
When enabled, if an Outlook task has a reminder
date/time set then this is used to set the
Google event start date/time. A reminder is also
set on the Google event 1 minute before the
start of the Google event.
If a Google event occurs at a specific time (not
all day) then the event start date/time is used
to set the Outlook task start AND reminder
date/time when synced from a Google event to an
Outlook task.

v2.1.15.0 - May 2010
|
|
 |
-
FIX: Corrected issue in the Google
client libraries used by gSyncit that prevented
a more detailed error from being returned when
using g-zip compression for faster communication
with Google services.
-
FIX: Corrected issue where syncing a
reminder time larger than 4 weeks causes an
error during the sync of calendar events. Google
does not support reminders of more than 4 weeks.
gSyncit will sync the reminder using the maximum
allowable Google reminder time when the Outlook
reminder exceeds 4 weeks.
-
FIX: Improved the option with the sync
on startup so that Outlook does not freeze for a
moment when Outlook is still loading and gSyncit
attempts to access Outlook information.
-
PARTIAL FIX: Corrected a recently discovered
issue where syncing yearly recurring events to
the Google calendar causes a java script error
on the Google calendar interface. gSyncit has been updated
to try to work around some of this issue. The
issue still exists for creating yearly events
that occur on the Nth weekday of the month. A
Google calendar defect has been filed for this
issue.
http://code.google.com/p/gdata-issues/issues/detail?id=2013
-
FIX: Corrected several reported typo's
on the configuration/settings dialog.
-
FIX: Corrected issue using
the category sync option to _not_ sync items
assigned to a specified Outlook category. In
prior versions when a previously synced item is
later assigned to category that should not be
synced the item was not properly deleted from
Google calendars/contacts/documents. This
fix addresses this issue such that when a
previously synced item is
assigned to a group that should be _excluded_ from
the sync then the Google item is now deleted.
-
FIX: Corrected issue where the Outlook
profile selection dialog was not properly
appearing when the gSyncit tray app was loaded.
This caused the tray app to return an error when
attempt to access settings outside of Outlook.
This error caused the following dialog to appear
when attempting to access settings from the
gSyncit tray app.

-
UPDATE: Added the ability to set the
default contact address selecting in Outlook
when update a contact.

-
UPDATE: Added the ability to enable/disable mappings from the
main mapping listing panel to avoid have to open each mapping and
use enabled checkbox option.

-
UPDATE: Updated the
calendar/contact/note/task mapping list to
clearly show the account name as part of the
Google path information so that it is easier to
see which Google account is being used.
-
UPDATE: Moved the import/export
options from the dialog menu to buttons on the
settings dialog to make it easier for users to
import/export settings.

-
UPDATE: Added multi-select option for
deletes to make handling multiple
delete operations easier to manage.

-
UPDATE: Added "Normal" as one of the
available visibility options when importing
items from the Google calendar. This allows the
visibility for Google items to be overridden
when written to the Outlook calendar and appear
as "Normal".

-
UPDATE: Added support for syncing task
reminders with Google calendar events. This
includes being able to turn on/off the reminder
sync and setting the default reminder type when
creating Google events.


-
UPDATE: Changed the order that task
fields are synced with Google events. Since most
users seem to set the Status and Important value
more often these values have been moved to the
top. The fields are listed as follows...
Status: Complete
Importance: High
PercentComplete: 100
DateCompleted: 4/28/2010 12:00:00 AM
ActualWork: 1
TotalWork: 2
Complete: True
Status: Complete
-
UPDATE: Added option to the
calendar defaults allowing for the default
reminder type to be applied to new AND existing
items allowing new and existing items to have
the same reminder type.

-
UPDATE: Added dialog to the mappings
when clicking OK that indicates all items
associated with the mapping will be re-synced.
This reset process has always occurred. Ading this this dialog simply makes this
event know to the user and helps explain why the
sync takes a long time after changing settings.
v2.1.12 - April 2010
|
|
 |
-
CHANGE:
Set the default g-zip compression option on the
communications options to false. For
many users having this option turned on caused
'(400) Bad Request' errors during the sync. This
option works under a normal network
configuration. However, in a corporate network
this option tends to cause problems.
Additionally, when this option is on certainly
details of a '(400)' bad request error are not
displayed that is otherwise helpful to diagnose
this error.
-
FIX:
Corrected issue where the category for Outlook
2002 and 2003 users was not displaying correctly
when using the drop-down list to select a
Outlook category.
-
FIX:
Corrected issue with contact name matching where
if the Gmail contact name contains a space at
the end of the name it would fail to match with
an existing Outlook contact.
-
FIX:
Corrected recurring event time zone sync issues
with users in Tokyo. gSyncit incorrectly set the
time zone to "Asia/Tokyov".
-
FIX:
Corrected '(400) Bad Request' error when any
user defined Gmail contact fields were populated
with empty spaces from an Outlook contact. For
example, if the Outlook field 'Office Location'
contains a value of a single space character
then the Google contact service returns a 400
error.
-
FIX: Corrected issue
where user is unable to abort the sync during
delete operations that occur at the end of the
calendar sync process.
-
CHANGE: Updated the
error messages to include additional Google
error information to help diagnose Google
related errors.
-
FIX: Corrected
reported '(417) Precondition Failed' errors
during the calendar sync process.
-
CHANGE: Moved options
from the connection settings panel to a new
'General' settings panel.

-
CHANGE: Added new
configuration option to assist Outlook to exit
to resolve issues where Outlook remains running
in the background as a result of gSyncit being
loaded into Outlook. This basically includes
some of the "smarts" of the Shutdown Addin
product into gSyncit.
-
FIX: Corrected
reporting issue where users in countries not
using AM / PM indicator encountered incorrect
delete requests for items that occurred at the
start or end date specified for a sync date/day
range. Events that occurred before 12:00PM on
the start of the sync range and events that
occurred after 12:00PM at the end of the sync
range would trigger a prompt for deletion. To
work around this issue simply set a AM and PM
indicator on the windows date/time settings.
This fix no longer requires this work around.
-
FIX: Corrected issue
where events from Google to Outlook that have
the same start date/time and subject were not
correctly being synced to the Outlook calendar.
The first event would sync correctly while all
others would be incorrectly marked for deletion.
-
FIX: Corrected "The
recurrence pattern is not valid." when setting
the MonthOfYear on an Outlook event. This error
typically occurs when updating birthday type
events using a specific recurrence structure.
-
CHANGE: Added the the
ability to reset sync history by mapping type
rather than having to reset the sync history for
all mapping types.

v2.1.10 - March 2010
|
|
 |
-
CRITICAL CONTACT
CATEGORY/GMAIL GROUP SYNC ISSUE -
Resolved reported issue with syncing Gmail groups with
Outlook categories related to a change recently
made to the Google Gmail contact service.
gSyncit uses a URI (e.g. 'http://www.gmail.com/....') path as a Gmail group
identifier. Until recently this identifier
included a protocol reference that matched the
same protocol used to access Gmail based on the
contact mapping Google account settings. For
example, when using SSL (secured connection) the Gmail group
identifier would be returned with the "https"
protocol specification. It was recently
discovered that this is no longer the case and
the "http" protocol specification is now being
returned for SSL based requests.
The net result is that this change is breaking
gSyncit's ability to sync Gmail contact groups
with Outlook categories. gSyncit is attempting
to match the group identifiers assigned to a
Gmail contact with those returned from the main
Gmail group list to obtain the group
name that is then used to set the Outlook
category. Being that the protocols between the
value returned from the GMail contact group assignment
and then Gmail group list no longer match
gSyncit cannot properly determine the Gmail
contact group assignment causing issues with the
Gmail group/Outlook category syncing.
To resolve this issue gSyncit now excludes the
protocol specification from the Gmail group
identifier.
In researching this issue I found a related
posting from Google that notes this exact issue but for
contact IDs.
Fortunately gSyncit does not rely on protocol
information for contact identifies since v2.1
was released. However, the change noted in the
posting proposed for March 31st matches the
exact change that was noticed March 28th. I can only
guess that Google made this change to the group
functionality without notice.
http://www.google.com/support/forum/p/apps-apis/thread?tid=1cc6d99077e5a34b
v2.1.9 - March 2010
|
|
 |
-
CORRECTION -
Resolved reported issue where when gSyncit is
installed recently used email address
information was not retained when Outlook was
closed.
-
ENHANCEMENT
- Added the ability to sync Outlook user
defined properties with a Gmail contact. This
option is disabled by default and allows for
syncing user defined properties for Outlook
contacts with user defined Gmail contact
properties. This change allows users switching
from the Palm/Outlook sync to
Droid/Outlook/Google sync to retain all
information in Gmail that the Palm sync adds to
Outlook contacts and any other applications that
use Outlook contact user defined fields.

-
ENHANCEMENT
- Added additional Outlook fields to the
contact sync process. These fields include
User1, User2, User3, User4, CustomerId,
ReferredBy, GovernmentId, and BillingInfo. These fields will appear in a Gmail
contact a user defined values. Additionally,
Outlook contact car and fax phone numbers have
been added to the sync logic.
-
ENHANCEMENT -
Changed the default connection options to
use keep-alive to help improve connection speed
with Google.
-
ENHANCEMENT -
Updating the logging functionality to help increase
the speed of the sync process.
-
FIX - Corrected
issue where Outlook contacts are missing the full
name when being updated from a Gmail contact that
has a company and name that are the same.
v2.1.8 - March 2010
|
|
 |
-
AUTO UPDATE SETTING ISSUE
- Corrected reported issue that turning _off_ the check
for updates does work and gSyncit continues to prompt for
updates when available.
-
CONFIGURATION ISSUE -
Corrected issue where the option to only
sync uncategorized options was being incorrectly reset when
loading the settings dialog.
-
FREE/BUSY EVENT ISSUE
- Corrected issue where newly created Google free/busy
events were created with a start date/time of the current
date/time.
-
CONTACT COUNTRY INFO
- Corrected issue where gSyncit was not properly syncing
country with Gmail contacts.
v2.1.5 - March 2010
|
|
 |
-
RECURRING EVENT ISSUE
- Addressed a reported issue where occasionally a non-recurring
item in Outlook would turn into a Weekly recurring item.
I'm still not exactly clear on why this randomly happens
but I hope this fix does the trick. The "fix" simply clears
the outlook recurrence state when Google event is not marked
as recurring.
-
PRECONDITION FAILED -
Corrected issue related to 412 errors when duplicate
contacts exist in Gmail. I thought this issue has been resolved
in prior versions but this appears to be a defect in the
Gmail contact service. If the same contact is updated multiple
times very quickly the Google service will return this error.
I was able to work around this bug by disabling the Google
concurrency checking and forcing gSyncit to always replace
the existing Gmail contact as it should.
-
SYNC PERFORMANCE -
Reduced logged information to resolve reported performance
issues with the sync process. Even with the reduced the
logged information it appears that Google response time
slows down as the number of contacts in Gmail increases.
As the number of contacts exceeds 100 it appears to take
about 1-2 seconds to insert/update a contact record. Based
on an average of 1 seconds per contact this means that 1000
contacts will take about 15 minutes to sync over a fast
network connection.
-
DUPLICATE REMOVAL OPTION
- Added configuration option to calendar, contact, task,
and note mappings to allow gSyncit to delete any duplicate
items. The default option is to not remove duplicates. In
v2.1.4 support was added to allow for duplicates but apparently
people actually liked that gSyncit cleaned up duplicates
in prior versions so I've added an option to turn this functionality
back on.

-
SYNC ONLY UNCATEGORIZED
ITEMS - Added configuration option to calendar, contact,
task, and note mappings to allow only syncing Outlook items
that are NOT assigned to any categories. Any item that does
not contain a category will get synced. This option allows
uncategorized items to easily be synced to a different calendar
from those items assigned to a category.

v2.1.4 - March 2010
|
|
 |
-
SUPPORT FOR DUPLICATE
ITEMS - Added support for duplicate calendar, contact,
notes and task entries. In prior versions gSyncit would
attempt to delete any duplicate entries and someone contributed
to 400 and 412 errors during the contact sync process. No
harm was done to any data since the deleted items were duplicates
and most users were able to work around this issue by manually
removing the duplicates.
Duplicates records also caused delete requests at the end
of the sync to remove the duplicate items. After recent
delete issues with the calendar these delete requests gave
users a bit of a scare and questioned the validity of the
calendar sync process when all it was doing was removing
duplicates.
Now that gSyncit supports duplicate entries this should
no longer be an issue, however, it is recommend to avoid
duplicate entries when possible.
gSyncit will match entries between Outlook and Google to
avoid creating duplicates. However, if duplicate records
existed in one location and only one record existed in the
other then gSyncit would map all the duplicates to a single
record. At the end of the sync gSyncit would remove all
the "extra" duplicates which is why users are seeing the
delete dialog appear during the sync. To validate this when
the delete dialog appears check the Outlook or Google location
where the item is going to be deleted and you _should_ see
duplicate items.
In v2.1.4 these extra delete dialogs should no longer occur
now how gSyncit will allow for duplicate entries. This was
actually something that Gmail did not support and was never
an issue during the sync process. It appears that Google
has changed their policy and now allow for duplicate Gmail
entries. Gmail also includes a nice feature to merge duplicates
which may be of use to many.
-
IMPROVED UPDATES NOTIFICATION
- Updates the sync process to check for any critical
updates before perform the sync process so that users can
be alerted to any critical sync issues before syncing. Critical
updates will direct the user to a webpage with details on
any issues and halt the sync process.
Just after gSyncit checks the internet connect it then checks
for any software updates and or critical notices. If a critical
update is available then the the sync process is halted
and the user is redirected to a web page with information
on why the sync process has been halted. If an update is
available the user is prompted for the update.
This notification process will interrupt and suspend the
automatic sync process by design given that software updates
are consider critical and should be applied as soon as possible
before data is synced.
My goal here is to be able to "pause" the network of gSyncit
users as soon when I am alerted to any issues with the sync
process. I will keep it "paused" until I can provide a fix
or provide guidance to help protect user data.
v2.1.2 - March 2010
|
|
 |
-
Corrected the contact delete
dialog to properly show the company name or email address
when a contact does not contain a full name. Currently there
are cases where the delete prompt shows "Deleted Contact[]"
which makes it difficult to determine which contact is being
deleted.
-
Corrected delete related
issue which caused a "(400)" and/or "(403)" error during
the contact sync process.
-
Corrected "Index and length
must refer to a location within the string. Parameter name:
length" when an error is encountered. The actual error is
captured in the log file but this error message is displayed
to the user.
-
Updated the contact sync
logic to prevent possible future delete issues with contacts.
The contact sync uses the record id portion of the contact
ID rather than the full URI.
-
Forced the option to check
for product updates to be on.
v2.1.0 - March 2010
|
|
 |
-
CRITICAL/MAJOR FIX - Resolved issue where
calendar events were being deleted from the Outlook calendar
after a recent change to the Google calendar services. gSyncit
uses the URI to Google events as an identifier that includes
the protocol used to access the event. When SSL mode is
turned on the path notes the https protocol. Starting March
2, 2010 the event URI is being returned with the "http"
protocol vs. the "https" protocol. When gSyncit performs
a sync and reads Google events it fails to matches the "https"
id with the "http" and considers the item to be deleted.
I have since updated gSyncit to use a different identification
value for events that no longer requires using the event
URI and protocol specification and an identifier.
v2.0.38 - March 2010
|
|
 |
v2.0.37 - February 2010
|
|
 |
-
Correct performance issues
related to syncing multiple Google accounts with the same
Outlook contact and Notes folders. In prior releases items
would incorrectly be updated when the item was not actually
modified.
-
Corrected reported 403 error
that occurred when updating Google calendar events that
were read-only.
-
Corrected issue syncing
yearly events that occur on a specific month on days of
the week (mon,tue,wed..) causing the error "The recurrence
pattern is not valid." Notes below is an example of this
recurrence pattern that failed to update into Outlook.
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=1MO,1TU,1WE,1TH,1FR
v2.0.35 - February 2010
|
|
 |
-
Corrected issue which caused
the Outlook security guard dialog to appear during automatic
syncing.

-
Corrected reported "object
reference not found error" when accessing the gSyncit settings
from the gSyncit tray app while Outlook is not running.
-
Corrected issue changing
the task prefix set on the task mapping. This value was
not properly saved/restored when modified.
v2.0.34 - February 2010
|
|
 |
-
Rebuild to address Outlook
security prompts with v2.0.33.
-
Corrected "object reference
not found error" when accessing Gmail contact postal addresses.
-
Corrected issue deleting
items when using a sync date range of one day.
v2.0.33 - February 2010
|
|
 |
-
Resolved reported issues
where the sync process kicked off multiple times causing
various sync issues. This issue was introduces in a previous
beta version.
-
Minor update for syncing
monthly recurring events from Google calendar.
-
Updated reported issues
with auto sync with specified time frame.
-
Added last sync date to
the settings dialog
-
Added option to sync tasks
to Google calendar by Due Date only. The current default
logic is by start date.
-
Updated calendar mappings
to properly initialize settings for read-only Google calendars.
-
Added a retry process to
reading documents from Google to resolve timeout issues
when reading data from Google.
-
Corrected reported issue
with the option to continue on error not working in all
cases.
v2.0.27 - February 2010
|
|
 |
v2.0.26 - February 2010
|
|
 |
-
Corrected reported issue
where the option to sync on Outlook exit was not consistently
occurring.
-
Corrected minor issue with
the verify connection button on the connection panel not
reporting back correct status/error information.
-
Updated the check for updates
prompt to take the user to the main v2.0 product updates
/ change log page.
v2.0.24 - February 2010
|
|
 |
v2.0.23 - February 2010
|
|
 |
-
Corrected issues related
to Outlook not closing on exit when gSyncit is installed.
-
Corrected "(403)" error
when updating recurring events in the Google calendar that
are part of a recurring event owned by another user. This
error basically occurred when updating read-only recurring
event exceptions.
-
Corrected issue where duplicate
contacts were created when using the option to set the Gmail
contact full-name to company name. When this option was
set gSyncit failed to match up Outlook contacts with existing
Gmail contacts. Additionally, when gSyncit updated Outlook
contacts the full name was incorrectly being set to the
company name when this option was enabled.
-
Corrected reported issue
were Gmail contacts were not being properly deleted after
being deleted from Outlook. When the Outlook contact was
deleted the delete would sync but the item would not be
deleted from Gmail. If the item was deleted a second time
it would finally be deleted from Gmail. This issue has now
been resolved.
-
Corrected issue where when
prompted to delete a contact containing only a company name
the delete message showed the contact name as "[]" making
it difficult to confirm the delete.
-
Corrected issue with the
notes sync where continuing on error cased "object reference
not found error".
-
Reduced the number of calls
to Google when updating a contact photo. The extra calls
were to work around issues with the Google contact service
that have since been resolved by Google.
-
Updated the calendar sync
logic such that if a Google event is marked as busy and
an Outlook event is marked as Out-of-Office then the Outlook
event will retain the Out-of-Office indicator when the Google
event is synced to Outlook.
-
Added configuration allow
existing contact photos to be overwritten. When this option
is turned off then gSyncit will only update a contact photo
if one does not already exist. When this option is turned
off this will prevent existing contact photos from being
updated/overwritten. To preserve Outlook contact photo image
quality this option should be turned off.

-
Added configuration option
to include/exclude Outlook tasks without a due date from
the sync.

v2.0.20 - February 2010
|
|
 |
-
Improved the performance
of the Outlook Notes / Google Document sync now that Google
has resolved a defect that required gSyncit to use a workaround
to cleanup duplicate documents after inserting a document.
Google had a defect where when a document was inserted Google
would create a random number of duplicates of the document.
gSyncit would then delete the duplicates. This delete process
is no longer needed and has been removed.
-
Added sync details to the
log that shows how many items were added, updated, delete,
and read for the sync process.
-
Added option on the sync
options settings panel to enable/disable loading gSyncit
on windows startup. Optionally, right-clicking the gSyncit
tray app and selecting auto start will stop gSyncit from
loading at startup.
-
Corrected a reported issue
syncing Outlook tasks marked as repeating where they would
not sync to Google Calendar in some cases.
-
Addressed "(417) Expectation
Failed" by defaulting the "Expect 100-Continue on request
responses" option to turned off for new installations. Recently
Google made some change that has caused a number of users
to start seeing this error with the same version of gSyncit
that was working in the past. This solution is discussed
on the gSyncit support page.
v2.0.19 - January 2010
|
|
 |
-
Corrected reported issue
with the 'FileAs' option applied to the contact sync where
duplicate items appear in the Outlook contact list due to
a failure to match Gmail contacts with existing Outlook
contact full names. If a Gmail contact name is last, first
then gSyncit fails to match the Gmail contact with a full
name of 'first last'
-
Updated the task mapping
dialog to note that it is recommended that a dedicated Google
task calendar be specified for storing tasks. Some users
found this confusing and ended up syncing tasks to their
main calendar causing a great deal of unexpected headaches.
-
Added option to the calendar
and task settings to enable/disable allowing items to be
deleted.
-
Corrected issue where a
"just-in-time (JIT) debugging instead of this dialog box."
message is displayed when the gSyncit error dialog has an
error being created.
-
Updated the registration
process to make it a little more clear about how to upgrade
using a v1.0 product key in combination with an upgrade
key.
-
Corrected an Outlook security
issue where Outlook was not able to locate gSyncit's trusted
digital signature on all components. This issue caused Outlook
to fail to load into Outlook and in some cases cause the
Outlook Object Model Security Guard dialog to appear during
the sync process.
-
Corrected reported error
"You changed one of the recurrences of this item, and this
instance no longer exists. Close any open items and try
again." which occurred when updating recurring event exceptions.
This issue was thought to have been resolved in the v2.0.17
release build but the change never made it into the official
release.
v2.0.17 - January 2010 (Major Release)
|
|
 |
-
Task Sync : Outlook Tasks
<-> Google Calendar Sync. Added the ability to syncing
of Outlook tasks
with user defined Google Calendars.

-
Category drop-down list
on the Category tab for each feed mappings now show all
available categories when using Outlook XP and Outlook 2003.
-
Added "Out of Office" default
to the available defaults that can be set when creating
new Outlook events. Because Google does not offer a similar
option and Outlook events marked as "Out of Office" will
continue to be synced to Google calendar as "Busy".

Historical Product Change
Logs
|