For Sugar® and Exchange: AESync
Filtering SugarCRM Items
A common synchronization requirement is to filter CRM items that need to be synchronized.
Read MoreSynchronizing Categories
What we want to do is to map the Outlook Field ‘Category’ to the Custom CRM field ‘Type’.
Read MoreTransferring Server
It is a common requirement to be able to move the synchronizer to the new system.
Read MoreCustom Fields
Custom fields are commonly used in SugarCRM to allow handling custom type of data. Simple example is ‘Middle Name’ field that is available in the Exchange and missing in the SugarCRM. Below we are going to demonstrate how to enable middle name synchronization.
Read MoreSetup Impersonation for Office365 2013
Exchange account used for synchronization must have rights to impersonate all users in the synchronization profile.
Read MoreSynchronizing Recurring Events
Recurring events may have different structure in SugarCRM and Exchange, so proper synchronization requires smart handling.
Read MoreExchange 2010 Impersonation for User Group
Sometimes assigning “Full Access” permissions in Exchange is not possible due to company security policy. So we need a flexible way to set “ApplicationImpersonation” permission for connecting user to cover a specific list of users (synchronized mailboxes) in Exchange.
Read MoreGrinMark Account for Office 365
GrinMark Synchronizer needs just one Office 365 account to connect to Exchange and synchronize data for user's mailboxes. This account does not even need an Office 365 license. The only requirement for the account is ApplicationImpersonation admin role.
Read MoreAdding More Users to AESync Cloud
Adding new user to a synchronization profile is a simple procedure. Here we describe how to prepare users and add them to the profile for synchronization.
Read MoreSet Office 365 Password to Never Expire
GrinMark synchronization server needs a working uninterrupted connection to Office 365 to ensure stable and prompt synchronization of data. By default user passwords expire in Office 365 within 90 days. So you may want to make GrinMark user password to never expire. To achieve the goal follow these steps.
Read MoreMeeting Name Field Size Limit in Sugar
By default Name field of a meeting in Sugar has size limit of 50 characters. When a meeting with long subject is synchronized from Exchange to Sugar - the subject is truncated. This may lead to duplicates in Sugar. Learn how to avoid such an issue.
Read More