In Dynamics CRM, the Regarding field was set to the contact instead of the account.
In Riva's connection to Dynamics,
Near the top of the Attendee Syncing page, this check box was cleared: "Inherit settings from SmartConvert".
On the Attendee Syncing page, under Advanced Options, this check box was selected: "Assign to Account of matched Contacts".
In Outlook, a user would send an appointment inviting a contact that existed in Dynamics CRM.
Expected result: In Dynamics, the appointment's Regarding field would be set to the account.
Actual, defective result: In Dynamics, the Regarding field was set to the contact.
Now, as expected, in Dynamics, the appointment's Regarding field is set to the account.
UI improvement: Background: The ability introduced in Riva 2.4.53, sync a non-CRM-contact in the To field to the CRM without creating a contact, had to be configured with an advanced option. Now, it can be configured by selecting a check box in the Dynamics 2011+ connection edit window. Specifically, on the Options page, the check box to select is Appointment: Add unmatched attendee email address.
Deleting an Outlook contact is now synced as clearing the Sync to Email Client check box: Previous behaviour: In a very specific configuration, when a contact was deleted in Outlook, it was deleted in Sugar. Now, when a contact is deleted in Outlook, it is not deleted in Sugar. Instead, the contact's Sync to Mail Client check box is cleared in Sugar. The contact is retained in Sugar and will not be synced back to Exchange or Office 365, unless the Sync to Mail Client check is re-selected in Sugar.
An email address that was deleted in CRM was correctly removed from one Outlook field but still appeared in another.
A contact in CRM had multiple email addresses and one was deleted in CRM.
Expected results in Outlook, on the Contact tab: The deleted email address would be removed from both the Email drop-down field and the Display As field.
Actual result: It was removed from the Email field but still appeared in the Display As field.
Now, the deleted email address is removed from both Outlook fields.
Fixed defect in Sugar sync to Exchange or Office 365:
When a lead was converted to a contact in Sugar, the contact was created in Exchange or Office 365 but the lead was not removed from Exchange or Office 365.
Now, in Exchange or Office 365, the contact is created and the lead is removed.
Ability to encrypt the results of a connection test with a certificate and save the results as an .xml file:
After running a test, selecting Save with Encryption opens the Select Certificate dialog box. The results are saved in an .xml file.
The .xml file can be viewed without having to be on the Connection Test page of the Riva Manager application.
The certificate does not need to be the same as the certificate used for the connection.
If the certificate is missing when attempting to view the file, an error message box appears.
Easier way to temporarily restrict the sync to one or a few users:
Possible purpose: Testing a sync configuration change on a few test accounts. Background: In previous versions, a cumbersome process was required. Now, a right-click in the sync policy opens a window where you can enter the only users you want to sync for the time being.
For instructions and a known issue, see Sync only one or few Riva users.
New for the Limited Resync re-init option. More intuitive way to set the advanced options that are required for Limited Resync: Previously, the advanced options for Limited Resync had to be copied and pasted manually on the Advanced Options page of the sync policy. Now, after Limited Resync is selected, one click brings up two lists to select the advanced options from. See Limited Resync in Riva 2.4.54.