General Topics

Basic Authentication and Exchange Online

GrinMark products rely on Exchange Web Services API (EWS) to access Exchange mailbox data. For a long time we use Basic Authentication to connect to Exchange with username/password combination. Since Microsoft has plans to disable Basic Authentication for all Exchange Online tenants in the second half of 2021 and already disables Basic Authentication by default for new Exchange Online tenants since October 2020 there are certain steps you need to do to continue using GrinMark services in the future.

Testing Exchange Service Account

GrinMark Synchronizer does not need mailbox passwords of individual users. Instead it uses single Exchange account (called Exchange Service Account) to connect to Exchange via EWS API and impersonate required users. In order to test Exchange connectivity Microsoft developed a handy tool Remote Connectivity Analyzer.

Exchange Web Services and Two-Step Verification

GrinMark products rely on Exchange Web Services API (EWS) to access Exchange mailbox data. More and more customers start switching to two-step authentication and as a result synchronization stops working. User credentials which worked previously lead to an ‘Unauthorized’ response from Exchange. To fix this generate an application password and use it with your GrinMark synchronization solution. It will work for individual users as well as for accounts which use impersonation to access other mailboxes.

Linked Contacts Field in Outlook

Outlook has a useful feature called Contact Linking. It enables you to link a contact with an appointment, task, other contacts, or email. Learn how to enable it in Outlook 2013, 2016.

Contacts Folder in Address Book

When you use your address book to select recipients for an e-mail message or attendees of a meeting in Microsoft Outlook, information from your custom Contacts folder (e.g. `CRM Leads` or `CRM Accounts`) does not appear in the list. Learn how to fix this.

Sugar and Exchange Sync

Filtering SugarCRM Items

A common synchronization requirement is to filter CRM items that need to be synchronized.

Synchronizing Categories

What we want to do is to map the Outlook Field ‘Category’ to the Custom CRM field ‘Type’.

Transferring Server

It is a common requirement to be able to move the synchronizer to the new system.

Custom 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.

Setup Impersonation for Office365 2013

Exchange account used for synchronization must have rights to impersonate all users in the synchronization profile.

Synchronizing Recurring Events

Recurring events may have different structure in SugarCRM and Exchange, so proper synchronization requires smart handling.

Exchange 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.

GrinMark 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.

Adding 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.

Set 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.

Meeting 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.

Sugar and Google Apps Sync

Google API: Increasing API Quotas

This topic describes the steps needed to resolve an AGSync issue reported as follows: Daily Limit Exceeded. The quota will be reset at midnight Pacific Time (PT). You may monitor your quota usage and adjust limits in the API Console…

Dynamics CRM and Exchange Sync

Filtering Dynamics CRM Items

A common synchronization requirement is to filter CRM items that need to be synchronized.

Salesforce and Exchange Sync

Shared Activities

Considerations for Shared Activities (Multiple Contacts on an Activity) | Salesforce

Grant Login Access to GrinMark Support

Simple steps to grant access to Salesforce organization for GrinMark support team.

Install and Launch

Simple steps to get GESync up and running.

Install GESync Managed Package into Salesforce Org

Install GESync into Salesforce Org in a few easy steps.

Filtering Salesforce Items

A common synchronization requirement is to filter CRM items that need to be synchronized.

Outlook 365 Plugin for Sugar

Setup with Exchange Server 2013 (on-premises)

How to install the plugin to on-premises version of Exchange Server.

Work with Outlook 2016 on MAC

Insight to the plugin functionality on MAC OS X.

Install and Launch

Simple steps to get GrinMark Outlook 365 Plugin for SugarCRM up and running.

TextMiner

Install TextMiner from Office Store

Installation of TextMiner add-in for Office 365.

The token is not valid after (error message)

Describes how to deal with an error message about invalid token.