W-Systems joins SugarCRM! Read Blog
Added custom option for the sync policy to enable attachment sync from Exchange to Goldmine.
Availability: Riva 188.8.131.5213+
Learn more: How to enable attachment sync support for Exchange to GoldMine.
Support for all-day appointments
Added support to sync untimed appointments and phone calls from GoldMine to Exchange as all-day appointments.
Availability: Riva 184.108.40.20697+
Learn more: How Riva syncs GoldMine calendar items to Exchange.
Appointments completed by another user were not synced as "Completed" for the original user's Outlook calendar.
Solution: Riva now removes the calendar item from the original user's Exchange calendar if it is completed in GoldMine by another user.
Availability: Riva 220.127.116.1106+
Learn more: How Riva syncs GoldMine calendar items.
IsClosed support for opportunities
By default, Riva detects when opportunities are closed and removes AssignTo drop folders.
Availability: Riva 18.104.22.16805+.
Example: For an example company, the closed status can be Won (default) or Completed (which is equal to "Win") or Lost (default) or Aborted (which is equal to "Lost").
To use the enhancement as per the example: Set the following custom options for the Sage CRM connection:
Sync.Crm.IsClosedRegex.Opportunity = Won|Lost|Completed|Aborted and
Crm.ClosedItemTombstoneDelayInHours.Opportunity = 0.
Using SmartConvert to create opportunities from different recipients from the same email domain produces multiple identical account records. This occurs for Sage CRM 7.1+ due to a CRM schema change.
Solution: Upgrade Riva to 22.214.171.12447+.
Caution: The upgrade does not merge previously created account records.
Emails with attachments were not synced.
Solution: Upgrade Riva to release 126.96.36.19995+.
Riva did not move processed emails from email drop folders back to the Inbox or Sent Items folders.
Solution: Upgrade Riva to release 188.8.131.5275+.
Excess accounts and/or contacts
When converting an email to create an opportunity (by processing an email in the - Create New Opportunities folder), Riva created multiple accounts and contacts. Specifically, if Riva synced an email that had no matching CRM contact, Riva created an account and/or contact, created the opportunity, and created a second account and/or contact.
Solution: Upgrade Riva to release 184.108.40.20647+.
Salesforce has announced that effective Jan 1, 2016, API connections will not be able to resolve www.salesforce.com in connections.
Login.salesforce.com must be used instead.
Solution: Upgrade to Riva 220.127.116.11666+, in which the Riva Salesforce connection automatically uses login.salesforce.com.
Learn more: Riva provision for: www.salesforce.com API endpoint will be retired on January 1, 2016.
New custom options enable an optimized preloading of contact photo info, so that API calls are not wasted. This also improves performance.
Availability: Riva 18.104.22.16860+.
Learn more: Salesforce: How to enable syncing of contact photos.
An event with a reminder caused the "The added or subtracted value results in un-representable DateTime" error.
Solution: Upgrade Riva to release 22.214.171.12495+.
Country and state pick lists
If a customer enabled country and state pick lists in Salesforce (Setup => Data Management => Country and State pick lists), but a contact's country and/or state values did not match the values on the pick lists, Riva reported an error when attempting to sync that contact
Solution: Upgrade Riva to release 126.96.36.19913+, which contains a custom option to configure Riva to support country and state pick lists.
Learn more: Custom option to support Salesforce country and state picklists.
Timezone error for Argentina/Buenos Aires
Riva reported an "Unable to find matched timezone America/Argentina/Buenos_Aires" error.
Solution: Upgrade Riva to release 188.8.131.5212+, which includes a timezone mapping for America/Argentina/Buenos_Aires.
New custom fields not recognized
Continued "INVALID_FIELD_FOR_INSERT_UPDATE: sObject contains invalid fields" error conditions consumed extra API calls to force Riva to do a Salesforce lookup to confirm that new custom fields were valid.
Solution: Upgrade to Riva release 184.108.40.20679+. New custom fields are now permanently added to the CRM connection metadata.
Backing up transaction records
New app.setting options applicable to .config files specify the scheduled automated backup of a transaction file to a specified target location at specified intervals.
Availability: Riva release 220.127.116.11965+.
Learn more: How to implement automated transaction backup.
Attachment custom options
The custom options that control attachment sync by using specific category names are now effective at the service-engine level. This means that Sync.Crm.Attachment.IncludeCategory and Sync.Crm.Attachment.SkipCategory work for both Exchange and Notes.
Availability: Riva release 18.104.22.16872+.
The Crm.DaysAllowedForDelete.Task option can now be applied to the sync policy.
Availability: Latest 2.4.39 release.
Appointment start times
Riva now logs the appointment start time for each sync event in user local time by default. If the user's timezone is not available, Riva optionally shifts the timezone to the server local time. If the user's local timezone is not available, the server local time should be the default. Logs show the Start Date in 2015-02-11 13:00-07:00 format if the timezone is local or any defined timezone (for example Eastern or Central), and it uses the format 2015-02-11 20:00Z for UTC.
Availability: Riva release 22.214.171.12444+.
Learn more: Custom option to set logging to record appointment start times in UTC only.
Protection for email address changes
If a user was assigned to a sync policy as a member of an email group, the email address for the user could have been changed in the email system and the CRM without renaming the user in the sync policy, which would accidentally start a new sync for the user and create duplicates.
Solution: Upgrade Riva to release 126.96.36.19981+. Riva now reports an error when the situation is detected, so that the user can be renamed in the sync policy for a proper sync.
Re-init option to clear CRM User ID conflicts
When a CRM user ID conflict was encountered, an admin was expected to copy the old metadata to the new metadata. Then the admin had no way to resume the sync.
Solution: Upgrade Riva to release 188.8.131.5209+. Riva now has a re-init option that can be selected to bypass the check for the next sync cycle and allow the sync to resume.
Learn more: Synchronization failed due to Crm ID conflict. <> already registered for another user.
This release of Riva includes special options that only Riva Professional Services can enable and configure. To request any of the following features, contact the Riva Success Team.
Exclude sensitive info from metadata
New custom options prevent Riva from storing sensitive information like names or email addresses in the transaction metadata. Riva hashes the data and uses the hashes for lookups.
Salesforce default record types
A new custom option can be applied to set the default record type based on the user profile pulled from the CRM user record.
Cached CRM connection
By default, Riva clears the cache of the CRM connection information once every 24 hours. If you need the clear cache interval changed, contact the Riva Success Team.
Salesforce plug-in migration and/or compatibility
New custom options can be applied to the .config file to sync calendar items with the Salesforce plug-in for Outlook installed.