{"id":516,"date":"2015-03-20T12:58:11","date_gmt":"2015-03-20T12:58:11","guid":{"rendered":"http:\/\/www.portatour.com\/blog\/users\/?p=516"},"modified":"2015-03-23T10:21:33","modified_gmt":"2015-03-23T10:21:33","slug":"new-synchronization-settings-in-dynamics-crm-last-customer-call-date-addresses","status":"publish","type":"post","link":"https:\/\/www.portatour.com\/blog\/users\/en\/2015\/03\/20\/new-synchronization-settings-in-dynamics-crm-last-customer-call-date-addresses\/","title":{"rendered":"New Synchronization Settings in Dynamics CRM: Last Customer Call Date, Addresses"},"content":{"rendered":"

With today’s update of portatour\u00ae for Dynamics CRM you get two new synchronization settings.\u00a0Download the update now from our\u00a0download-page<\/a>.<\/p>\n

Initialize Last Customer Call Date<\/h2>\n

When you first start to work with portatour\u00ae, you may see customers suggested for a visit who have recently been visited by you. This can be avoided by telling portatour\u00ae the correct date of the\u00a0“last customer call” for a customer.\u00a0If you already have this date\u00a0stored somewhere in your CRM, then this new feature makes it easy to\u00a0initialize it.<\/p>\n

\"\"<\/a><\/p>\n

Navigate to “Settings” and then to “portatour\u00ae \u2013\u00a0Administration” and “Synchronization Settings”.<\/p>\n

Choose from which entity portatour\u00ae should read the date of the last visit. In the following example,\u00a0we are using a\u00a0date field of the\u00a0\u00a0“Appointment” entity. Click “Edit query” to create a view and define the filter:<\/p>\n

\"\"<\/a><\/p>\n

In this example I am looking for the date of the last appointment at this customer to use it as “last customer call date”. Only appointments\u00a0from the last year should be included, I use the “Start Time” field to filter older and upcoming\u00a0appointments out.<\/p>\n

Hint: Limit the “last customer call date” to a time frame which is in a realistic\u00a0relation to the “call interval”. For example, using the last year. If you allow\u00a0dates far away in the past, customers who have not been visited for years suddenly become very urgent\u00a0to visit and portatour\u00ae\u00a0will primarily\u00a0suggests to visit these outdated customers before anyone else.<\/em><\/p>\n

The view\u00a0must also contain a criteria relating the entities to an example account <\/strong>\u2013 in the above case, the appointments are related\u00a0to the account “Koch, Simone”. You define\u00a0the view\u00a0as a template which works for one account, portatour\u00ae will then apply it to find the correct “last call date” for all\u00a0synchronized accounts. You can decide which example customer you use in the filter.<\/p>\n

The view must return exactly one column with date values<\/strong>. Any additional columns with other data types are ignored by portatour\u00ae. I am using the “Start Time” column of the appointment, which contains both the time and the date of the visit. To ensure that the latest appointment is picked, I configure the sorting<\/strong> of the results to sort by “Start Time” in “Descending Order”. portatour\u00ae will read the date from the\u00a0the first returned row.<\/p>\n

\"\"<\/a><\/p>\n

Summing up, these are the four requirements to consider when writing\u00a0this view:<\/p>\n