Quantcast
Channel: Dynamics 365 Customer Engagement in the Field
Viewing all 103 articles
Browse latest View live

Dynamics 365 Monthly Update-January 2018

$
0
0
Quick Links: Featured News | Updates and Releases | Training Corner

Featured News


Scheduling the Microsoft Dynamics 365 (online) version 9.0 Update

Here is some information to help customers prepare for updating their existing Dynamics 365 (online) organizations to Dynamics 365 (online) version 9.0:

What you need to know about the customer-driven update process:

Flexible choices: You can schedule your updates to Dynamics 365 (online), version 9.0 on any day, including weekends. Please remember that opportunities to schedule an update is limited to available openings. Update slots will be allocated on a first come, first served basis.

Scheduling an update: Scheduling an update is available now and the updates will occur from February 20th through August 20th. This will give you up to six months to complete the update to the newest release of Microsoft Dynamics 365.

Flexible testing: Administrators will be able to schedule updates to sandbox instances prior to production instances. You can easily see the Sandbox and Production update schedules in a single view within the Dynamics 365 Administration Center.

Keep your organization informed: Administrators can select recipients to receive notifications about updates in the Dynamics 365 Administration Center. See Send email notifications to multiple recipients for more information. The recipient does not have to be an administrator to receive notifications and no additional licenses are required.

Get yourself ready for the update:

1. Get familiar. Stay up to date with What’s new for the complete list of capabilities and services. Please refer to Read Me for more information about update requirements, known issues and possible workarounds.

2. Get prepared. Read about Managing updates.

3. Get engaged. Your partner and Microsoft are here to help you be successful. See What’s new for developers.

Note: Dynamics 365 Government and Dynamics 365 Germany are not included as part of this announcement. The availability of version 9.0 for these customers will be announced later.


Continued support for Outlook add-in (Dynamics 365 for Outlook)

In June 2017, Microsoft announced the deprecation of Dynamics 365 for Outlook (also known as the “Outlook add-in”) and the plan to replace it with Dynamics 365 App for Outlook. The deprecation announcement meant that Dynamics 365 for Outlook would continue to be supported until it was removed in Dynamics 365 version 10.0.

Since this announcement, Microsoft has received overwhelming feedback from customers, partners, and the Dynamics community around the need for the Outlook add-in. Additionally there are some feature gaps in Dynamics 365 App for Outlook which prevent it from being a viable replacement for the Outlook add-in. As a result, Microsoft is reversing the deprecation of Dynamics 365 for Outlook.

This announcement means that Microsoft will continue to release Dynamics 365 for Outlook with new versions of Dynamics 365. As a result, customers upgrading to a new version of Dynamics 365 will have the same Outlook integration experience as in previous versions.

For more information, view the announcement on the Dynamics 365 Customer Engagement Team Blog.


Preparing for a new era in privacy regulation

On May 25, 2018, a European privacy law, the General Data Protection Regulation (GDPR), is due to take effect. The GDPR imposes new rules on companies, government agencies, non-profits, and other organizations that offer goods and services to people in the European Union (EU), or that collect and analyze data tied to EU residents. The GDPR applies no matter where you are located. New GDPR white papers are now available that provide details on how Microsoft Dynamics applications can be an important part of the journey toward GDRP compliance. The currently available white papers are for the Customer engagement applications (Dynamics 365 for Sales, Dynamics 365 for Customer Service, Dynamics 365 for Field Service, and Dynamics 365 for Project Service Automation). Go to http://aka.ms/gdprdynamics365 to find the links to the available Dynamics 365 GDPR white papers and check back often to find new GDPR info and updates to existing white papers.

Visit the Microsoft Trust Center to learn more about how Microsoft’s products can help customers comply with the GDPR and to find resources like webinars, videos, white papers, FAQs about the regulation.


Back to top

Updates & Releases


Updated SDK Tools required for Dynamics 365, version 9.0

As mentioned in a recent Blog and KB article, Dynamics 365 (online) version 9.0 no longer supports TLS 1.0 or 1.1. Customers with older versions of the Dynamics 365 SDK, will need to download the latest versions from NuGet:

https://docs.microsoft.com/en-us/dynamics365/customer-engagement/developer/download-tools-nuget

Older versions of SDK tools such as the Plugin Registration Tool, will not connect successfully to Dynamics 365 (online) version 9.0 organizations. Additional information can be found here on the Microsoft Support site.


Connect Dynamics 365 CRM for Outlook Client 8.x to Dynamics 365 9.x instances

With the release of Dynamics 365 Customer Engagement version 9.0, older versions of TLS (1.0 and 1.1) connections will be blocked and only connections using TLS 1.2 will be supported. For customers connecting a Microsoft Dynamics 365 for Outlook client on version 8.x to a Dynamics 365 9.x instance, an update will be required for the clients.

Please refer to the following articles for details:

Updates coming to Dynamics 365 Customer Engagement connection security

“There is a problem communicating with the Microsoft Dynamics 365 server" error occurs when configuring Microsoft Dynamics 365 for Outlook


Missing App URL Suffix after importing app via a solution

Below is a documented issue a customer experienced shared to the Dynamics CRM in the Field:

Scenario: A customer created an application in Dynamics 365 8.2 and added an App URL Suffix to access the app directly at "https://<crm instance name>.crm.dynamics.com/Apps/<AppName>". Next, the customer wanted to move the app via a solution file to a higher instance (ie: Dev to Test). They created a solution file and added the App and sitemap to the solution. Then they exported the solution and imported into the higher instance.

Result: The application imported successfully. However, the App URL Suffix was blank and greyed out so the customer couldn’t add it back in the App Designer | Properties area.

This is “by-design” as there isn’t currently a way to detect if an App URL Suffix is already in use in the destination instance. When this is cleared, customers can still access their application by going to the My Apps area, but they can’t access it directly via the URL in the source instance.

A suggested resolution for this issue has been submitted to the Dynamics 365 Ideas site: https://ideas.dynamics.com/ideas/dynamics-crm/ID0003757 Customers can vote on this resolution for higher visibility to the product team.

Workaround: The good news is that there is a workaround that exists in both Dynamics 365 8.2 and v9.0 today. Customers can go to the My Apps area (https://<crm instance name>.crm.dynamics.com/Apps) | Locate your App | Select “Manage Roles” | Expand “App URL Suffix”. From there you can enter the desired URL in the destination instance, save and publish. This will allow access directly to the app from the URL again.


Voice of the Customer Service version 9.0.1027.16

Voice of the Customer for Dynamics 365 version 9.0.1027.16 is live on all Geos. This version of Voice of the Customer is compatible with Dynamics 365 version 8.2 and later.

New and updated features include:

· The reliability and experience of survey delete operation are improved. All the dependent entities of a survey are deleted when the survey is deleted.

· Customers can now repair or restore the Voice of the Customer configuration if it is accidentally deleted or misconfigured.

Resolved issues include:

· The tooltip of a question for a few languages (ex. Chinese, Russian, Farsi, Arabic) was not translated properly.

· The field names in survey response mapping and workflows does not match.

· The survey entity interface is not translated properly in French locale.

For more information, see What’s new in Voice of the Customer version 9.0.1027.16.


Microsoft Social Engagement 2018 Update 1.1

Microsoft Social Engagement 2018 Update 1.1 is now available.

New and updated features include:

· Improved accessibility across all interfaces to include keyboard navigation, screen reader support and overall improvements to the user experience.

· Administrators can now remove recipients from alerts that were configured by other users

· Changes for author information from Facebook pages to support updated API

For more information, see What’s new in Microsoft Social Engagement 2018 Update 1.1.


Field Service and Project Service Automation Update 5

The latest update to the Field Service and Project Service Automation solutions for Dynamics 365 version 8.2 is now available. This update includes improvements to quality, performance, and usability, and is based on customer feedback and requests.

Field Service enhancements (7.2.0.43)

Resolved issues include:

· Users with an administrative license type that own records received an error about privileges when upgrading from Dynamics 365 8.1 to 8.2

· Option to disable Address Suggestions doesn’t work

· Unable to create contact, opportunity, lead, account, or case entities in an updated organization

· When editing any field on a product receipt, the user sees the error message: System status can't be changed manually to products received or billed

· Cannot partially receive a purchase order product

Project Service Automation (v1.2.3.16) Enhancements

Resolved issues include:

· Contract line detail updates only display after refreshing the page

· Time entry date is set to the next day after the user saves or refreshes, if the user's timezone zone is far in the future (UTC+13 or UTC+14)

· Expense_Amounts lose decimal precision when the decimal separator is not a period (.)

Universal Resource Scheduling Enhancements

Note: Improvements and bug fixes for Universal Resource Scheduling apply to Field Service and Project Service Automation as well as to other schedulable entities in the Sales or Service applications.

Resolved issues include:

· Lookup selectors render incorrectly on screens with lower resolutions or when browser zooming is enabled

· Can’t create a booking alert if user is under a child business unit

· Can't book a schedulable entity that has no requirement

For more information, review the Release Notes for Field Service and Project Service Automation Update Release 2 post in the Dynamics 365 Team blog.


Dynamics 365 Digital Assistant Experiences

Microsoft is discontinuing the current Cortana integration preview feature that was made available for Dynamics 365. The focus will be on building a new long term intelligent solution experience, which will include Cortana digital assistant integration. The end result will be a robust and scalable digital assistant experience across all the Dynamics 365 offerings, to include natural language integration for customers and partners across multiple channels.


Back to top

Training Corner


Features list for Dynamics 365 (online)

To review the list of features that are available for Dynamics 365 (online) and to access the complete list of online vs. on-premises features of Dynamics 365, review the following article on the Dynamics 365 Documents site.


Microsoft AppSource for Dynamics 365 (online)

Dynamics 365 online customers have the ability to add tailored solutions to their instances via AppSource. Customers can find top business solutions for their industry created by Microsoft and select partners. Apps include a try before you buy option and trusted Microsoft partners are standing by to assist with implementation.

For information on how it works, take a look at this tour.


Microsoft Dynamics 365 Webinar Series

Join the Microsoft Dynamics team to learn how the Dynamics 365 Customer Engagement solutions can revolutionize your customers’ digital transformation. In this webinar series, attendees will learn how to position Microsoft’s business solutions and differentiate their organization from the competition.

Upcoming Topics

· Understanding Dynamics 365 Add-Ons (Relationship Sales, PowerApps, CDS, etc…)

· Delivering a sizzling demo

· Dynamics Partners’ Resources/Pricing & Licensing

· Enhancing Microsoft Dynamics 365 with Azure + Intelligence (Bots, AI capabilities, etc.)
Leveraging Azure IaaS with Dynamics 365

Register now: https://aka.ms/microsoft-dynamics-365-webinar-series


Plan to attend Showcasing Dynamics 365 Demos

Note: This event requires a login to CustomerSource/PartnerSource

As a follow up to the November 2017 Microsoft Dynamics 365 Sales Blitz, the Showcasing Dynamics 365 Demos will be provided on February 12th at 8am and 8pm PST. We’re excited to share the demo strategy and resources as well as showcase the great innovations in Dynamics 365. Subject matter experts will be on hand to answer questions and on-demand sessions will be made available following the live-streamed event.

The complete agenda will be available soon along with registration information. Follow up with your Microsoft Account Manager for more details.


Back to top

Dynamics Portal content coming soon

$
0
0

We are excited to announce that starting this week Dynamics Portal content will be coming to the Dynamics CRM in the Field blog.  The authors are a mix of MCS consultants and PFEs, so the content will range from development to troubleshooting to taking advantage of new features.  The first post will be later this week and will discuss the in place upgrade process of ADX 7.0 to Dynamics Portal 8.0.

Dynamics 365 Monthly Update-February 2018

$
0
0
Quick Links: Featured News | Updates and Releases | Additional News

Featured News


Dynamics 365 Customer Engagement (online) API limits

Beginning March 19, 2018, Microsoft will limit the number of API requests made by each user, within an organization in Dynamics 365 (online). This change will affect all versions of Dynamics 365 (online).

Each user will be allowed up to 60,000 API requests within five minutes. This limit will help ensure that users running applications that make extraordinarily large demands on servers will not affect other users.

Some of the typical scenarios where this would happen are:

  • A plug-in that is written to pump data in a loop, without a well-defined max termination limit.
  • An inefficient client application that queries for status on thousands of records, without any caching or without any interval between successive requests.

For more information and guidance about this limit, please see API Limits.


Security Enhancements: User session and access management

New Security enhancements have been added to Dynamics 365 (online) version 9.0 to better secure the application. The enhancements are: set session timeout and set inactivity timeout.

clip_image001

User session timeout

By default, Dynamics 365 (online) sets a user session timeout of 24 hours. A user is not required to log in with their credentials for up to 24 hours regardless of whether the user was active or inactive. Administrators can now enforce users to re-authenticate after a pre-determined period by modifying the user session timeout.

Inactivity timeout

By default, Dynamics 365 (online) does not enforce an inactivity session timeout. A user can remain logged in the application until the session timeout expires. System Administrators can modify this behavior.

For more information on how to configure these features in Dynamics 365 (online), view the following article.

NOTE: These security enhancements are also available for:

Microsoft Dynamics CRM 2016 (on-premises, version 8.2)

Microsoft Dynamics CRM 2016 (on-premises, version 8.1)

Microsoft Dynamics CRM 2015 (on-premises)

Details on these versions can be found here.


Migrate from Adxstudio 7 to Portal Capabilities for Dynamics 365

As announced in September 2017, product support for legacy Adxstudio Portals v7 will end on August 1, 2018. A guide is now available to help customers migrate their portal solutions and configuration data stored in Dynamics 365 organization into the schema and format supported by Portals capabilities for Dynamics 365. The migration guide for customers on Adxstudio version 7.0.0025 and above can be downloaded from here.

Details about Portals capabilities for Dynamics 365 can be found here. For any questions, contact your Microsoft representative, your partner or adxquest@microsoft.com.


Back to Top

Updates & Releases


Notes on upgrade for Field Service and Project Service Automation

After upgrading to Dynamics 365 (online), version 9.0, customers will need to upgrade their existing Field Service and Project Service Automation solution to the latest version. To update to the latest solution, visit the Admin Center for Dynamics 365 online, access the solutions page and install the update. For details, refer How to Install, Update a Preferred Solution. Known issues for the application can be found here.


Field Service and Project Service Automation Update Release 4

The latest update to the Field Service and Project Service Automation solutions for Dynamics 365 version 8.2 is now available. This update includes improvements to quality, performance, and usability, and is based on customer feedback and requests.

Field Service enhancements (v7.4.0.74)

Resolved issues include:

• Error message received when editing any field on Product Receipt or when changing PO status to Products Received

• End Date on Agreement was incorrectly updated when start date is in DST but end date is not

• “Address Not Found” error when selecting address from suggestion popup

Project Service Automation (v2.4.0.48) Enhancements

Resolved issues include:

• Contract confirmation was not correctly processing unbilled actuals coming from journals

• Estimated cost on project entity page did not include expense estimates

• Resource Requirement created from the Generate Project team with tasks with decimal hours were off-by-one end date

Universal Resource Scheduling Enhancements

Note: Improvements and bug fixes for Universal Resource Scheduling apply to Field Service and Project Service Automation as well as to other schedulable entities in the Sales or Service applications.

Improvements for Universal Resource Scheduling can be viewed at What’s new in Universal Resource Scheduling for Dynamics 365 February 2018 Update.

Resolved issues include:

• Problem when switching between horizontal and vertical hourly schedule boards when a resource name is populated in the schedule board resource search box

• Issue with loading default saved filters on Schedule Board

• In the booking requirements grid, users can now filter to show requirements that do not have a value in the territory field

For more information review the Release Notes for Field Service and Project Service Automation Update Release 4.


Upgrade from the Interactive Service Hub to the Customer Service Hub

The Interactive Service Hub (ISH) was introduced with Microsoft Dynamics CRM Online 2016 Update 1 and Microsoft Dynamics CRM 2016. ISH offered a web-based client to simplify daily tasks for Customer Service Representatives and Managers. It included interactive dashboards, interactive forms, and reference panel control. Though the ISH intuitive interface combined vital information in one place and allowed Customer Service Representatives to prioritize work and be more productive, there were certain limitations in extending it. The new Customer Service Hub (CSH) available in Dynamics 365 (online) version 9.0, offers even greater flexibility and improved controls and extensibility.

New features include:

• An interactive interface that is an App Module featuring a new Custom Control Framework

• Unified Interface that eliminates the prolonged initial metadata download

• Easy to filter forms, dashboards, and other metadata components shown to business users

clip_image002

For more information about the new features and how to upgrade, review this article.


Microsoft Social Engagement 2018 Update 1.2

Microsoft Social Engagement 2018 Update 1.2 is now available. With this update, a feedback dialog is included for a sample of users when they sign in. Everyone is encouraged to provide feedback to help shape the service.

Resolved issues include:

• Fixed an issue to enable replies containing special characters on LinkedIn from within Social Engagement.

• Improved the search setup for keyword search rules to explain how to enter keywords, inclusions, and exclusions. Additionally, we list the limitations for keywords, inclusions, and exclusions per search rule.

• Improved the Message Center to explain more clearly that post alerts are sent every few hours, and not immediately after a specific post matches the configured alert.

Visit the Help Center for more information.


Portal Capabilities for Microsoft Dynamics 365 version 8.4.0.275

Portal capabilities version 8.4.0.275 is now available.

New features include:

• Access to detailed error logs for any issues with the portal

• Administrators are notified about the portal authentication key expiration and can renew it via the Portal Admin Center

• Portal Administrations can configure the General Data Protection Regulations to meet their organization’s needs.

All new features and resolved issues can be viewed here. For a full list of all portal update releases please reference this KB article.


Unified Service Desk version 3.2.0

The Unified Service Desk (USD) 3.2.0 release is now available. The latest version of USD has major enhancements on performance diagnostics, faster load times for CRM entity pages and graceful handling and recovery of crashed or unresponsive Internet Processes. For more information review this article on the Microsoft Dynamics CRM Unified Service Desk blog.


Back to Top

Additional News


Replicate Microsoft Dynamics 365 (online) data to Microsoft Azure SQL Database

The Dynamics 365-Data Export Service is an add-on service available on Microsoft AppSource that can be used to replicate Dynamics 365 (online) data to an Azure SQL Database store in a customer-owned Azure subscription. The Data Export Service intelligently synchronizes the entire Dynamics 365 data initially and synchronizes it on a continuous basis as changes occur in the Dynamics 365 (online) system. The supported target destinations are Azure SQL Database and SQL Server on Azure virtual machines. For more information on the Data Export Service and its requirements, review this article on the Microsoft Docs site.


Machine learning implementation strategy for a customer service center

With the digitization of almost all industries on the way, advanced technologies like machine learning are revolutionizing the way of work for most industries today. Many customer service centers are thinking about adopting machine learning for their day to day operations. These techniques will soon be a part of industry standard best practices.

Customer service leads can leverage various machine learning capabilities to meet their Key Performance Indicators (KPIs). Examples include task automation, relevant Knowledge Base article suggestions, similar cases suggestion using text analytics and proactive notifications to engage with customers.

This post describes how traditional call centers can create a strategy for adopting machine learning capabilities.


Preview: Dynamics 365 for Marketing

Microsoft is happy to announce the Dynamics 365 for Marketing is available in public preview for organizations seeking a marketing automation solution to generate more demand and drive more sales.

Microsoft Dynamics 365 for Marketing is designed as the front end of the sales cycle to help companies nurture more sales-ready leads, align sales and marketing and make smarter decisions. Most importantly, Dynamics 365 for Marketing works together with Dynamics 365 for Sales on the same platform which aligns teams with common data, connected processes and Office 365 collaboration tools. For more information and to sign up, view this announcement.


Preview: Dynamics 365 Support Center

Microsoft is happy to announce the launch of a new Help + support ticketing experience for admins to contact a Microsoft support representative for Dynamics 365 (online). This feature is in preview so customers can get early access and provide feedback.

clip_image003

For more information, review this article on the Dynamics 365 Customer Engagement Team Blog.


Back to Top

In-place upgrade of ADX 7.x to Dynamics Portals 8.x

$
0
0

Recently the Product Group released a migration guide to move from Adxstudio v7 Portals to Portal Capabilities for Dynamics 365.  That announcement with a link to the guide can be found here.  On the heels of that announcement I wanted to share my experience with doing an in-place upgrade of ADX 7.x to Dynamics Portals 8.x.  The guide itself covers several migration options including reimplementation both self-hosted or Microsoft hosted as well as an in-place upgrade both self-hosted or Microsoft hosted.  I won’t go through the details of the process since it is very well covered in the guide, but I’ll point out some of the findings as a result of going through the process.

Cleanup Prior to Upgrading

It is worthwhile to do a little housekeeping prior to starting the upgrade process.  You may have artifacts that are no longer being used and this would be a good opportunity to address those items.  The upgrade process will “split” each of the existing web pages into 2 pages – a root page and a localized content page.  The issue that arises is that even inactive web pages will get split and will result in an inactive root page with an active content page.  This will result in unexplained “404 not found” errors on the upgraded portal and potentially navigation links that are normally not visible due to Access Control Rules being now visible.  If there are inactive web pages that can’t be removed prior to the upgrade, an advanced find can be used post upgrade to find inactive root pages that have an active content page.  Those content pages should also be deactivated.

Images that had a space in the partial URL were no longer rendered after the upgrade, so it may be worth while to search through the child files and update the partial URLs so there are no spaces prior to the upgrade process.  Remember to update the related link to the file wherever it is being used.

Uninstalling ADX Solutions

Having ADX 7.x solutions deployed alongside Dynamics Portal 8.x solutions is not supported (and would not work anyway for the most part) so part of the upgrade process will include uninstalling the ADX solutions.  Depending on what ADX portal package was originally deployed as well as what productivity packs were also deployed, it’s possible to have 20+ ADX solutions in Dynamics 365.  As you can imagine removing these with all the interdependencies can become quite challenging.  Fortunately there are 2 utilities that can help.

Determining Installation Order

FetchXML can be used to retrieve the installation order of the ADX solutions.  Ordering the results in descending order of the installedon field will yield the correct uninstall order of the ADX solutions.  Use the FetchXML statement below, replacing “orgname”, and “x” for the version numbers to reflect your organization to retrieve the ordered list. (I’ll give credit to the below information from here)

https://[orgname].crm[x].dynamics.com/api/data/v8.[x]/solutions?fetchXml=<fetch mapping='logical'><entity name='solution'><attribute name='installedon'/><attribute name='friendlyname'/><order attribute='installedon' descending='true'/><link-entity name='publisher' to='publisherid'><attribute name='customizationprefix'/><filter type="and"><filter type="or"><condition attribute='customizationprefix' operator='eq' value='adx' /><condition attribute='customizationprefix' operator='eq' value='msa' /></filter></filter></link-entity></entity></fetch>

Finding Dependencies

There may still be situations where a lingering dependency is blocking the solution from being removed (e.g. maybe an ADX field is being used in a workflow, etc.).  The Dependency Checker tool is useful for identifying the exact dependency (or dependencies) that needs to be addressed in order to remove the solution.  Use the following URL below replacing the “organization url” to reflect your organization and the “objectid” of the solution attempting to be removed.  You can use the list of solutions from the above FetchXML statement to get the object id of the solutions.

https//<organization url>/tools/dependency/dependencyviewdialog.aspx?objectid={b6d13943-0612-4e12-b878-8d7137ab5b07}&objecttype=7100&operationtype=dependenciesforuninstall

FetchXML in Liquid Templates

As part of tightening up security on the portal, executing FetchXML now requires entity permissions on any entity that is part of the fetch statement.  At least the Read privilege needs to exist on the entity.  No errors will result after the upgrade as an indication, the fetch will result in no records so the liquid template will not work as expected (e.g. – if there is logic looping through results, etc.).

SMS for Two-Factor Authentication

Twilio support (and SMS in general) has been dropped with Dynamics Portals.  The Product Group is moving more towards external authentication/identity providers and this may be the opportunity to start investigating that path if your application is leveraging local authentication with 2FA enabled.  Email is still an option for sending the security code.

Web Templates - new reference to Website Record

Web Templates are a common way to store JavaScript functions as well as Liquid Template code.  Web Templates now have a reference to a Web Site record.  This will initially be missing after the upgrade has completed which results in “not found” errors anywhere the web templates are being referenced.  Simply updating the Web Template records lookup to the Web Site record will resolve this.

CSS Class Differences

There are a few changes to the CSS classes that are being used throughout the Portal.  Sub-grids is an example that comes to mind immediately.  Depending on how much custom theming was done to the original portal, it may be necessary to make changes to your CSS to reflect the differences in the upgraded portal.  If you entries in the various Custom CSS areas, now may be a good opportunity to consolidate those into a single file and use that as a child file of the root page.

“Failed” Portal Provisioning

When I went through the last step of provisioning the portal against my Dynamics 365 instance the provisioning did not actually fail with an error, it just never seemed to complete and the portal itself would display the “getting things ready” page.  I’m fortunate enough to have access to the product group and we were able to determine what was happening.  This is touched on in the migration guide, but I’ll offer some insight below.

At two stages of the upgrade process you will be deploying portals solutions to your Dynamics 365 instance.  The first time this is done to upgrade your existing portals artifacts to their 8.x counterparts.  The last time this is done is to provision the Dynamics portal against your Dynamics 365 instance (which will most likely further upgrade any already installed portal 8.x solutions and possibly deploy some new ones).  As you are choosing the portal package to deploy in each of these steps, you should be consistent with the original ADX portal type that was deployed.  This is important because the package that was originally chosen when first configuring the ADX portal will dictate what the ID is of your Website record and when you do the final upgrade step of provisioning the Dynamics portal against your instance if the GUID of the package chosen during provisioning does not match the ID of the existing Website record, the provisioning process will always appear to be still provisioning.

The provisioning process should create a record under Settings –> Portals –> Settings named PackageImportComplete.  The value for this record needs to match the ID of the portal package you selected to provision.  If the Website Copy tool was used against the ADX portal, it’s possible that the object of your Website record will not match one of the standard IDs.  This (having a non-standard Website id) may or may not impact the creation of the PackageImportComplete record.  If the PackageImportComplete record is missing you will need to create it and set the proper value based on the portal package that was selected.  If the record does exist and the value does not contain the proper value based on the portal package selected, update the record with the correct value.  The portal package values are:



Type ADX v7 Dynamics Portals v8
Custom D78574F9-20C3-4DCC-8D8D-85CF5B7AC141 D78574F9-20C3-4DCC-8D8D-85CF5B7AC141
Community 2AB10DAB-D681-4911-B881-CC99413F07B6 2AB10DAB-D681-4911-B881-CC99413F07B6
Employee Self Service 9D3AEE93-0766-4548-B85F-F00EF4620798 10152FEB-F33D-4CBD-997E-F7A336C3B8BF
Partner 6D6B3012-E709-4C45-A00D-DF4B3BEFC518 6D6B3012-E709-4C45-A00D-DF4B3BEFC518
Event 0B48376D-F961-4154-8B54-FB278B5DACBE C0887167-3954-E611-80DC-00155D209102
Customer 51C9210D-998A-4A79-B3A4-848E858D5FC3 7B138792-1090-45B6-9241-8F8D96D8C372

Dynamics 365 Monthly Update-March 2018

$
0
0
Quick Links: Featured News | Updates and Releases | Additional News | Training Corner

Featured News


Microsoft expands cloud services in Europe and into Middle East

Microsoft is thrilled to announce the plan to deliver the Microsoft Cloud from our first datacenter locations in Switzerland and the United Arab Emirates and expand the cloud options for customers in Germany. The Microsoft Cloud in France is officially open with the general availability of Microsoft Azure and Microsoft Office 365. Dynamics 365 will follow in early 2019. Over the last three years, Microsoft has more than doubled the number of Azure regions available. As of today, Azure has more regions than any other cloud provider. We’ve announced a goal to be in 50 regions across the globe, including plans for 12 new regions.

Office 365 and Dynamics 365 also continue to expand the data residency options for customers with 17 geographies announced. The two products are the only productivity and business application platforms that can offer in-geo data residency across such a broad set of locations. Each datacenter geography, or geo, delivers a consistent experience, backed by robust policies, controls and systems to help keep data safe and help comply with local and regional regulations. Learn more in this announcement from Corporate Vice President of Microsoft Azure, Jason Zander.


Dynamics 365 is first SaaS solution granted JAB High P-ATO

Microsoft Dynamics 365 Government has been granted a FedRAMP High Level Provisional Authority to Operate (P-ATO) by the Joint Authorization Board (JAB) for its Customer Engagement services. This is the highest level of FedRAMP certification available.

FedRAMP provides a standardized methodology for assessing, authorizing, and monitoring cloud services for US Government agencies. Any agency that hosts federal data in the cloud must do so in a FedRAMP authorized cloud service provider (CSP) per the OMB memorandum on Security Authorization of Information Systems in Cloud Computing Environments. There are two ways to authorize a cloud service through FedRAMP: a Joint Authorization Board (JAB) provisional authorization (P-ATO), and through individual Agencies. The JAB consists of the CIOs from the DOD, DHS, and GSA.

The “high” designation allows agencies to use cloud environments for high-impact data. The high security requirements are used to protect some of the government’s most sensitive, unclassified data in cloud computing environments.

For more information, review this blog post.


Information about the upcoming Dynamics 365 Update 9.0.2

Microsoft is excited to announce the Spring 2018 release for Dynamics 365 and the Business Application Platform. Customers can expect a wave of innovation across the entire product line with hundreds of new capabilities and features in three core areas: business applications, intelligent capabilities infused throughout, and transformational application platform capabilities. Learn more in this announcement from Corporate Vice President of Microsoft Business Applications Group, James Phillips.

Watch the Business Applications spring launch event on-demand.

The Spring ‘18 release for Dynamics 365 (Update 9.0.2) is for Dynamics 365 online v9.0 and will be applied starting in April 2018. Key things you need to know can be found here.

A few things to note:

  • Any new organization created on or after April 2, 2018 will be provisioned on the updated version. Any updates from version 8.x to version 9.0 that are scheduled on or after April 2 will automatically get this update and no change of schedule is needed. For existing orgs running Dynamics 365 (Online) version 9.0.1 or higher, the update will start deploying on April 7 through the normal deployment process.
  • The update is primarily focused on performance and reliability improvements, but it also contains some new features. The new features are opt-in and will not change your default experiences. Download the Release Notes for more information on the new features.

Back to Top

Updates & Releases


Microsoft Dynamics 365 Online Releases

The March 2018 Service Updates for Dynamics 365 online versions 9.x and 8.x are now available. Click the hyperlinks below for more details.

Service Update 3 (v 9.0.1.0510) resolved issues include:

  • Importing a solution fails due to a BulkOperationLog.createdobjectidname.Length exception
  • Navigating through form tabs using Dynamics 365 for Mobile causes a blank page to be displayed in some areas
  • Knowledge Articles display HTML tags around content, causing the article to not display properly

Service Update 4 (v 9.0.1.0569) resolved issues include:

  • Opportunity Actual Close Date (actualclosedate) is incorrect after closing An Opportunity.
  • Unable to revise a Quote if the record is owned by a team
  • An Editable Grid appears blank when editing an in-line filtered view
  • A Form does not load if the form configured custom control was created in version 8.0, or 8.1, and then updated to version 9.0

Service Update 5 (v 9.0.1.0621) resolved issues include:

  • An Unsupported Type Conversion exception occurs when qualifying Lead records
  • Delete button doesn't render properly in sub-grids
  • Summary tabs on forms do not render expansion and collapsing properly
  • Adding a Marketing List to a Campaign Activity that is owned by a Team results in an exception

Service Update 5 (v 8.2.2.1161) resolved issues include:

  • An Unexpected Error occurs when using the SharePoint integration on Account entity records with names longer than 200 characters
  • An Invalid Parameter exception occurs when linking an Article to a Case record
  • Custom icons do not display properly on sub-grids
  • A change to a different Business Process Flow stage does not trigger Business Rules in the mobile client

Service Update 6 (v 8.2.2.1259) resolved issues include:

  • A Query Build exception occurs when accessing attachments on Appointments
  • The incorrect date and timestamp displays on OneNote pages opened via Dynamics
  • Date and Time rollup fields cannot be recalculated until the record is refreshed
  • Hyperlinks inside iframes are not able to be opened under certain conditions

Service Update 16 (v 8.1.1.1657) resolved issues:

  • Settings options are unavailable in the mobile client under certain conditions
  • The back button is not visible when searching for records on the Case entity in certain circumstances
  • An Unexpected Error occurs when configuring Dynamics for Tablets
  • Users are unable to change filter in the Option Set column for Editable Grids

Service Update 17 (v 8.1.1.1707) resolved issues include:

  • Workflow messages do not display properly when using the mobile client
  • An Unexpected Error occurs when opening or creating Application records in certain circumstances
  • Hyperlinks in iFrames are not able to be opened under certain conditions

Service Update 18 (v 8.1.1.1758) resolved issues:

  • Changes to increase performance on specific SQL queries
  • An Access Denied error occurs when reparenting Account and Contact records under certain conditions

Dynamics 365 App for Outlook version 9.0

The Dynamics 365 App for Outlook version 9.0 is generally available to all customer organizations on Dynamics 365 (online) version 9.0. Some of the new features in the App for Outlook include:

  • View tracked email or appointments in the App
  • Quick Create function to create new records without leaving Outlook
  • Pin and dock the App in Outlook desktop
  • Search in Dynamics 365

For more information on best practices for migrating from Dynamics 365 for Outlook (Outlook Client) to Dynamics 365 App for Outlook and additional links to comparisons and user guides, review this blog post.


Microsoft Social Engagement 2018 Update 1.3

Microsoft Social Engagement 2018 Update 1.3 is now available.

New and updated features:

  • The author tags filter now lets you exclude specific author tags from your data set.
  • Twitter extended its support for longer messages in November. For most languages, the same limits were in place. This update adds support for Korean, Thai, and Simplified Chinese language.
  • Social Engagement now supports retroactive deletion of posts that were acquired and deleted on the source afterwards. Posts from Twitter, Tumblr, and WordPress are now removed from Social Engagement when the author removes them from the source.

Visit Social Engagement Help & Training for more information.


Back to Top
Portal Capabilities version 8.4.0.277

Portal capabilities version 8.4.0.277 for Microsoft Dynamics 365 is now available. This release includes an updated portal host only. The portal host will be automatically updated by Microsoft.

This update resolves the issue with the login not working for users who were using a local login and had the Authentication/Registration/LocalLoginByEmail site setting set to true.


Deprecated: Portal capabilities for Dynamics 365

The following features are being deprecated from portal capabilities for Dynamics 365:

Web Page Tracking

Web Page Tracking logs a record when a user views a web page in a web browser. The date/time and user's IP Address are logged along with the identity of the user viewing the page. If the user is authenticated, the log is associated with the contact record related to the user, otherwise the anonymous identity is recorded. This functionality has a negative performance impact on portals.

Recommendation: Customers should use analytics technology like Azure Application Insights to capture this information.

Web File Tracking

Web File Tracking logs a record when a user downloads a web file in a web browser. The date/time and user's IP Address are logged along with the identity of the user downloading the file. If the user is authenticated, the log is associated with the contact record related to the user, otherwise the anonymous identity is recorded.

Recommendation: Customers should use analytics technology like Azure Application Insights to capture this information.

Authentication/LoginTrackingEnabled site setting

Enables or disables tracking the user's last sign-in. When set to true, the date and time are displayed in the Last Successful Sign-in field on the contact record. By default, this is set to false.

Recommendation: Customers should use analytics technology like Azure Application Insights to capture this information.

Portals solution versus 8.1.x.x

Solution version deprecation means that Microsoft will not be testing backward compatibility of these solutions with the latest version of portals code in future.

Recommendation: It is recommended to upgrade your 8.1.x.x solution to the latest version.

For more information on the deprecated features of Dynamics 365 portals, see this blog post.


Back to Top

Additional News


Improve On-Prem Dynamics 365 Performance with SQL 2016 Configurations

The following settings can help improve Microsoft Dynamics 365 application performance and should be configured on the SQL Server 2016 instance where the Microsoft Dynamics 365 organization databases are serviced:

  • Install the SQL Server 2016 Cumulative Update 2 (CU2)
    Server & Tools Blog: Cumulative Update #2 for SQL Server 2016 RTM
  • Configure the SQL Server instance where the Microsoft Dynamics 365 organization database is maintained with Trace Flag 1224. This setting disables lock escalation based on the number of locks and helps reduce CPU usage on SQL Server 2016. To determine the existing trace flag 1224 setting run the following T-SQL statement. A return value of 0 for status in the output indicates trace flag 1224 is not enabled:

DBCC TRACESTATUS (1224)

To set trace flag 1224 as a startup option, add the SQL Server database engine startup option -T1224. For more information: Database Engine Service Startup Options.

  • Configure Microsoft Dynamics 365 organization databases to use compatibility level 110, which is the compatibility level for SQL Server 2012. For more information: View or Change the Compatibility Level of a Database.
  • Configure the Microsoft Dynamics 365 organization database to use indirect checkpoints and a target recovery time of 60 seconds. By default, new databases created with SQL Server 2016 use indirect checkpoints and have a default target recover time of 60 seconds. For more information: Change the Target Recovery Time of a Database (SQL Server)

To determine the existing target recovery time, run the following T-SQL statement, where <dbname> is the name of the organization database. A return value of 0 indicates a target recover time has not been set:

SELECT target_recovery_time_in_seconds FROM sys.databases WHERE name = ‘<dbname>’

To set the target recover time of a database to 60 seconds, run the following T-SQL statement:

ALTER DATABASE <dbname> SET TARGET_RECOVERY_TIME = 60 seconds


What’s new in the Dynamics 365 admin center

With the introduction of Common Data Services for Apps, which leverages the same platform as Dynamics 365 for Customer engagement, PowerApp users are able to create Common Data Service instances that can be controlled and managed by the Tenant or Dynamics 365 Administrator. Customers with multiple environments and instances now have the ability to filter the instance list to Production, Sandbox, Trial or other instance types. For more information, review this blog post.


Knowledge Base Usage Analytics with Azure Application Insights and Power BI

When managing a self-service knowledge base in Dynamics 365, understanding how customers and employees are searching for and consuming self-service knowledge is an important part of ensuring your content remains relevant and useful for end users.

Dynamics 365 includes a number of in-built capabilities to help analyze the usage of the knowledge base, including:

  • Tracking of article views by source
  • Tracking of article ratings and feedback
  • Tracking of case deflections from knowledge
  • Tracking of articles associated with, or used in resolving cases

In some instances, you may wish to extend beyond the built in capabilities, to understand usage patterns to a greater depth: what your users are searching for, which searches are not returning any results, and how users are navigating through your Dynamics portal, for example. These metrics can be captured using Azure Application Insights and Power BI.

Take a look at this blog post for more details.


In-place upgrade of ADX 7.x to Dynamics Portals 8.x

The Product Group released a migration guide to move from Adxstudio v7 Portals to Portal Capabilities for Dynamics 365. Customers also have the option to do an in-place upgrade from ADX 7.x to Dynamics Portals 8.x. The guide goes into great detail on several migration options including reimplementation both self-hosted or Microsoft hosted as well as an in-place upgrade both self-hosted or Microsoft hosted. There are a few things to consider as part of the in-place upgrade such as clean up prior to the upgrade, determining installation order, finding dependencies and CSS class differences.

Review this blog post for more information on these considerations.


Blog Posts of Interest

The new business model: Relationship Selling

Relationship sales isn’t just for selling—How marketing can make an impact

Announcing Microsoft Dynamics 365 Business Central: greater impact with an end-to-end view


Back to Top

Training Corner


Dynamics 365 Customer Engagement Features

The Microsoft Docs site is the home for technical documentation, code examples, quick start guides and tutorials for developers and IT professionals. To learn more about the Dynamics 365 Customer Engagement features, applications, solutions and related services, visit the doc’s site here.


Dynamics 365 Portals 101 – Features, Use Cases and Best Practice

If you’re interested in using Dynamics 365 Portals, but don’t know where to start, take a look at this video that reviews the out-of-the-box features and use case scenarios for various portal templates. See capabilities of styling, configuring and customizing Portals via a demo and pick up a few tips, tricks, and best practices along the way to make your Portal projects a success.


Ideas for Microsoft Dynamics 365

Help us improve Microsoft Dynamics 365 and its family of products and solutions by discussing ideas, providing suggestions, and giving feedback. Use the forums listed on the Ideas page to share your thoughts. Search through the existing ideas, before suggesting a new one, and you can vote on them to help increase visibility.


Back to Top

Dynamics 365 Monthly Update-November 2018

$
0
0
Quick Links: Featured News | Updates and Releases | Additional News

Featured News


Dynamics 365 October '18 Update

The October ’18 wave of business applications released from Microsoft provides customers with significant capabilities to transform their business. These new services and capabilities include:

  • New intelligence applications that employ decades of AI work pioneered by Microsoft Research to make Dynamics 365 more intelligent. You can enhance sales performance and planning with the new Dynamics 365 AI for Sales application.
  • New Power platform capabilities that combine Power BI, PowerApps, Microsoft Flow and the Common Data Service for Apps into an unmatched palette of tools to extend, customize, and integrate Dynamics 365 and Office 365 into your environment.
  • Deeper integrations with other Microsoft products that offer seamless experiences with Dynamics 365 and Microsoft Outlook, Teams, SharePoint, Stream, Azure, and LinkedIn.

For more information, download the October ’18 Release notes here and review the following links:

What’s new in version 9.0

What’s new in version 9.0 for Developers

Online features for Dynamics 365 Customer Engagement

On-Premises features for Dynamics 365 Customer Engagement

Preview: Dynamics 365 AI for Customer Service

Dynamics 365 AI for Customer Service is a suite of products designed to help provide better customer service experiences through the power of artificial intelligence (AI). Microsoft is excited to announce the availability of Dynamics 365 AI for Customer Service Insights for public preview.

Features include:

  • Out-of-the-box dashboards that provide visibility into critical operational and performance metrics.
  • Automated grouping of cases by support topics, without the need for manual tagging.
  • Visibility into top case volume and resolution time drivers allowing users to focus on areas with highest impact.
  • Insights into emerging topics, allowing users to tackle issues before they become a major problem.

For more information on the features, review this blog post and start the preview at Dynamics 365 AI for Customer Service Insights.

Back to top

Updates & Releases


Microsoft Dynamics 365 Online Release

The November 2018 Service Update for Dynamics 365 online version 9.1.0 is now available.

Service Update 8 (9.1.0000.0829 or higher) resolved issues include:

· When attempting to view records for quote products in advance find, no values appeared when only a base money field was present.

· Optionset columns displayed backend integer values instead of text values.

· The lookup filter was not functioning in on-premises environments.

· The sequence number for products mismatched between Opportunities, Quote, and Order Lines.

· When merging two contacts, the first name and last name fields were not being selected by default.

Unified Interface Lookup Leverages Quick Find View

In response to feedback on the differences in search behavior between the legacy web client interface and the Unified Interface, Microsoft made changes to the Unified Interface's search behavior, so it aligns with the behavior of the legacy web client interface. Before the change, the Unified Interface used the lookup views for both the display view (defines the columns shown in your returned search results) and the search view (defines the columns against which the search is made). With the change, the Unified Interface now uses quick find views for the search view. Customers can now leverage the added performance of indexing in quick find views when specifying the columns for the search results.

If your organization currently uses the legacy web client interface, there is no change. For those upgrading to the Unified Interface, review this blog post for instructions on how to prepare for the change.

Universal Resource Scheduling Updates for Dynamics 365 v9.x

Microsoft is pleased to announce the latest updates to Universal Resource Scheduling, powering the Field Service and Project Service Automation applications for Dynamics 365. These releases include improvements to quality, performance and usability. To update your instance, visit the Admin Center for Dynamics 365 online, and find the solutions page to install the preferred solution.

This release is compatible with Dynamics 365 9.0.x.

Some of the resolved issues include:

  • In certain cases, map routes were not being displayed on the schedule board.
  • Issue finding availability for an onsite requirement when an approved time-off request overlapped with a booking.
  • Double booking a resource on multiday schedule boards now works as expected.
  • On the schedule board, zooming out with your browser now keeps rows properly aligned.

For more information on the features included in this release, review this blog post.

This release is compatible with Dynamics 365 9.1.x.

Some of the enhancements and resolved issues include:

  • When using the pop-out schedule board, the Dynamics border no longer loads, reducing confusion for users and improving performance.
  • Users can now search for characteristics and roles in the requirement group control.
  • When saving schedule board filters as default filters, a message now confirms the save was successful.
  • When deleting a resource, related resource territory records will be deleted as well.
  • Added missing hidden labels to schedule board filter panel targeting the accessible experience.
  • Schedule assistant no longer suggests times in the past when a resource has a capacity of greater than one.
  • The first requirement dragged to multiday schedule boards no longer causes an error message.

For more information on the features included in this release, review this blog post.

Field Service and Project Service Automation Updates

The latest update to the Field Service and Project Service Automation solutions for Dynamics 365 is now available. This release includes improvements to quality, performance, and usability, based on customer feedback and requests.

Field Service enhancements (v7.5.4.51) – This release is compatible with Dynamics 365 9.0.x

Some of the resolved issues:

  • HasUserPrivilege and HasTeamPrivilege should always execute using SYSTEM user context.
  • Updated the default Lookup View of the Service field on the Work Order Service.
  • Improvements to solution deployment and upgrade process.
  • Resolved script error on Work Order form in UCI Web.

For more information on the features included in this release, review this blog post.

Field Service enhancements (v8.2.0.286) – This release is compatible with Dynamics 365 9.1.x

Some of the enhancements and resolved issues include:

  • Enabled the ability to upgrade from previous versions of Field Service to Field Service version 8.
  • Enhanced Incident Types to enable the creation of types that require multiple resources by adding an Incident Type Requirement Group record.
  • Resolved failing button on Work Order Service Task – ‘Mark Complete’ sub-grid.
  • Added back deleted web resource msdyn_/Invoice/Invoice.Library.js.

For more information on the features included in this release, review this blog post.

Dynamics 365 for Marketing Updates

The latest update of Dynamics 365 for Marketing is now available. This is the first major update to the product since its release earlier this year. To benefit from this update, customers must manually apply it to each of their Dynamics 365 for Marketing instances as described in this article, Keep Marketing up to date.

New and updated features:

  • Account-based marketing: business-to-business (B2B) marketers can target each business account as a single unit, thus increasing integration and alignment between the sales and marketing departments.
  • Reusable content blocks: define and store reusable blocks of content with dynamic values from Dynamics 365 that are easy to add to email and page designs.
  • Social listening for campaign: analyze social-media channels to find relevant posts and evaluate user sentiment related to any topic you choose.
  • Marketing calendar for planning: provides a visual overview of any marketing activity that has a start and end date
  • Improved deliverability of email marketing messages: provides a way to register your Dynamics 365 for Marketing sending domain as a legitimate sender that does not get flagged for phishing.

For more information on the features included in the update, review this blog post. Review the Dynamics 365 for Marketing: Set up DKIM for your sending domain for more details on how to improve the performance metrics for delivered marketing emails.

Back to top

Additional News


Microsoft Dynamics 365 Return on Investment (ROI)

Microsoft has continued to expand and develop its portfolio of capabilities under the Dynamics 365 umbrella to support CRM, ERP, and human capital management (HCM) processes by integrating with Office 365, Power BI, PowerApps, and Azure. Nucleus Research conducted an analysis of customer case studies and identified that Dynamics 365 delivers $16.97 for every dollar spent, an ROI significantly higher over the industry average of $7.23 and $8.71 for both ERP and CRM, respectively. For more information, review the report.

Microsoft Dynamics 365 Customer Stories

Dynamics 365 Customer Stories
Customer Product Industry
Apollo Dynamics 365 for Customer Service, Microsoft PowerApps, Power BI Travel and Transportation
Hawkary Pharmaceuticals Power BI, Microsoft Flow, Microsoft PowerApps Professional Services

For more Dynamics 365 customer stories, visit this site.

PowerApps Customer Stories and Video Testimonials

The number of organizations adopting PowerApps to support their digital transformation continues to increase. This month Microsoft introduced new customer stories that illustrate how PowerApps apps are impacting customer operations.

PowerApps Customer Stories
Customer
Summary
Arriva
Using PowerApps to build apps that streamline one of the largest bus operations in the UK.
Eneco A Dutch energy company improving access to collaborative spaces and increasing productivity thanks to PowerApps.
North State Grocery Grocery chain in northern California and southern Oregon that created a custom app to boost their customer service program.
Leonardo Global Solutions A professional services company who's facilities management team has been able to improve efficiency by automating tedious, manual tasks at blazing speed.

Find more PowerApps customer stories here.

Back to top

Dynamics 365 Customer Engagement – Using Clone Solution to remove Managed Solution component(s)

$
0
0

Hey all-

You might have read some historical posts by me on my personal blog site here and team blog site here. Now I am part of Dynamics 365 PFE team focused on Customer Engagement. Here is my first post on CRM PFE Team blog site 🙂

Clone Solution feature has been around for a little while. However, I came across several customer questions around Clone Solution action and removal of managed component(s), entities or entity assets. For customers already familiar with Solution and Customizations, I created this guided lab showcasing simple example of Managed Component removal using Clone Solution and explains “Stage for Upgrade”. Presuming familiarity with Solutions and Customizations, this is not a full scale click by click lab document. For simplicity Dev and Test instances are Source and Target orgs, respectively.

In Dev Instance:

Create a New publisher named Contoso Consulting. Set prefix to CC

Create a new solution, named Providers. Set publisher to Contoso Consulting, version to 1.0

Under Providers solution,

  • Create a new entity named Provider with fields Name, Website, email address, work phone, fax and show it under Sales.
  • Create Agent entity under Providers solution with fields Name, email address, phone, fax, DOB and show it under Sales
  • Add Sitemap under client extension section
  • Export Providers solution as managed

 

In Test Instance:

Import Providers 1.0 solution.

Now switch back to Dev Instance:

Create 2.0 version of Providers solution by Cloning it

In cloned Providers v2.0 solution,

  • Remove DOB field from Agent entity
  • Remove Provider entity
  • Export Providers 2.0 solution as managed

In Test Instance:

  • Import Providers 2.0 solution.

Note: The “Stage for upgrade” check box on Import Options dialog allows separation of Solution Import and merging of both versions. It is checked and grayed out when there are Patches of same Solution in target instance. System enforces “Stage for upgrade” in such a scenario.

  • If there are no Patches of same solution in target system, “Stage for upgrade” is optional. When “Stage for upgrade” is selected (either by System or manual), Apply Solution upgrade action must be performed manually after the import. Apply Solution upgrade action is automatically executed as part of the Solution Import if “Stage for upgrade” is left unchecked.

  • If "Stage for upgrade" was selected, then Apply Solution upgrade when import is complete. Solution Import completion dialog offers this action, or it’s available on Solutions grid. This action is applicable for the previous version and not the recently imported(staged) _Upgrade solution, refer below screenshots.

Note: Behind the scenes the “Applying Solution Upgrade” action takes care of merging both version and retains only latest version, Providers 2.0 in above example. Post Apply upgrade, one can examine Providers 2.0 Solution for components removed.

Maintain or override customization doesn’t apply to removed component so one can chose depending on potential unmanaged changes in target org.

 

Hope this helps!

Bhavesh Shastri

Dynamics 365 App for Outlook Part 1- The Basics

$
0
0

With the recent release of the new version of Dynamics 365 App for Outlook in 2017 along with v9.0 and the new unified interface, there has been quite of bit of ongoing work to bring features and improvements in this area. As many organizations are now in the transition from the legacy Dynamics 365 for Outlook client, I have encountered many questions that I will address within a multi-part blog series in collaboration with Cody Dinwiddie. He is one of our Support Escalation Engineers on the Dynamics 365 Support team focused on email integration.

 

This multi-part blog series will be focused on a Dynamics 365 Customer Engagement (online) to Exchange Online environment. Although, much of this would also be valid for hybrid and On Premise environments.

 

There are multiple resources already available and I will do my best to link out to these through the series. The first important list of resources starts with the App for Outlook guide on the Docs site. This is a great starting point and most of the information included in the series will be in addition to what can be found in these guides.

Deploy the Dynamics 365 App for Outlook

Dynamics 365 App for Outlook User Guide

What's new with Dynamics 365 App for Outlook

 

What does it offer?

  • With the new unified interface, it offers the same experience as you will see in the new unified interface in a web browser and the mobile app. With the ability to customize the app, you can modify the sitemap to allow users full navigation of Dynamics 365 Customer Engagement.
  • View information about Dynamics 365 contacts and leads while you’re working in Outlook. You can view this info in the context of an email message, meeting, or appointment.
  • Track email messages, meetings, and appointments to a Dynamics 365 record with a single click. For example, link an email message to a specific account, opportunity, or project.
  • Open Dynamics 365 records directly to find or enter more detailed information.
  • Quick create of records
  • Relationship Assistant and Email Engagements
  • Global Category or Relevance Search
  • Add email templates, knowledge articles, and sales literature when you create an email message or set up a meeting.
  • Track Outlook contacts in Dynamics 365 and link to parent Account records

 

Let's talk about terminology

Set Regarding - Track and link the email or appointment to an existing record in Dynamics 365. This must be an activities enabled entity. When this is done, the record will appear in Dynamics under the user's activities views, related activities for any recipients who's email resolves to a Contact in Dynamics, and on the record selected for Set Regarding.

 

Tracking (without regarding)- Create a copy of the email or appointment in Dynamics 365. The difference between this and Set Regarding is that this is not attached to a specific Dynamics record and will show up only under the user's activities views and related activities for any recipients who's email resolves to a Contact in Dynamics. The creation of the record may also be referred to as promotion.

 

Email Filtering - Personal Options a user can configure to determine what emails will be tracked into Dynamics. We cover these starting in part 3 of this series

 

Email Correlation - This occurs after an email is filtered. The method which is used by Dynamics to determine if a received email is part of an email conversation that is already tracked, was automatically promoted by Server-Side Sync(i.e. folder-level tracking), or was sent from within Dynamics 365. This may also be referred to as email identification and matching.

 

Email Resolution or Association- This refers to the process which Dynamics uses to verify if the email address in the sender or recipients of an email or appointment match that of an email enabled entity, such as Account, Contact or Lead. We will talk more about this in part 4.

 

Synchronization - This refers to synchronizing emails, appointments, contacts, and tasks between Dynamics and Exchange. This may also be referenced when discussing the filters that control which records are synchronized as well as field synchronization, which controls the which fields and the direction each is synced.

 

Synchronous tracking - This means that the email, appointment, or contact is tracked immediately. It does not wait for the async service in Dynamics to retrieve the item to bring into Dynamics.

 

Asynchronous tracking - This is the opposite of above. This means that the record is not promoted/tracked immediately. It has been marked as an item to track and it will be tracked when the asynchronous process polls for items to bring to Dynamics. In this case, a user will see Track pending…

 

 

Requirements:

Since requirements may change with versions, I am simply providing the link to the Requirements doc site that is maintained by the product group. Be sure to take a look at these. They will also be covered in part 2 of this series.

Dynamics 365 App for Outlook requirements

If you just reviewed the requirements link above, you know that Server-Side Sync must be configured as a requirement for the Dynamics 365 App for Outlook. Aside from confusion with terminology, one of the most common questions I get is regarding the email that is sent from Dynamics upon successful configuration of a user's mailbox.

The issue? Every time a Dynamics mailbox is configured successfully, an email is sent to the user's mailbox. It looks like below:

 

This can cause confusion to the users that may not understand why they are getting this. Some users believe it is Spam and report it to their support/help desk. Especially in troubleshooting scenarios, where you may end up running through the Test and Enable process multiple times, this email will be sent every time. Currently, there is no way to either disable this email from being sent or any ability to modify the message that is sent in this email. However, here are two links for a Product Enhancement Idea if this is affecting you.

 

Need an option to Enable or Disable the functionality of sending Test Email when Testing and Enabling mailbox.

Customizable template for Server Side Sync Test and Enable email

 

With the current functionality, there are two options I have seen implemented.

  1. Configure an Outlook Rule for all users to delete this email when it arrives. This may briefly appear to the user before deleted.
  2. Configure an Exchange rule. From my testing, this was not noticeable to a user. I tested two rules and the criteria I tested with is in the screenshot below. Both rules worked to delete the message

How can I configure my Exchange mailbox to multiple Dynamics 365 instances?

You can't. This is another very common question I get about the mailbox configuration process. It is not possible to configure multiple Dynamics 365 mailboxes to the same Exchange mailbox, even if the mailboxes exist in different instances. Allowing this would result in synchronization, promotion, and correlation conflicts on individual items between the two instances.

 

Take a look at the related documentation here

 

If you need to test the same mailbox in lower environments prior to going live with this in production, just make sure it is disabled in other instances. If you are already live, testing in lower environments should only be done with mailboxes that are not configured in production, such as test users/mailboxes.

 

That wraps up part one of this series.

Stay tuned over the next two weeks for the rest of the series!

 

Aaron Richards


Dynamics 365 App for Outlook Part 2- What is supported?

$
0
0

For this part of the Dynamics 365 App for Outlook series, let's talk about what is supported.

 

At the time of this post, I am covering what is currently supported, including the specific features and clients for which they are available.

 

Here is the link to the Requirements documentation, which is updated and maintained by the product group, if at any time, this documentation becomes out of date.

 

The most common questions I receive in this area are:

  • Does the App for Outlook support Appointment or Contact tracking on the Mobile Outlook App? This is not available. It only supports Received Emails.
  • Can I use the App for Outlook in OWA on a mobile device? No, the App for Outlook is not supported on Mobile OWA for any feature.
  • Can I track tasks at all with the App for Outlook? No, tracking of Tasks is currently not available for the App for Outlook on any client
  • Why can't I access the add-in from OWA to track Contacts? Contact tracking is not currently available in OWA

Feature support per client

Received email

(view information and track)

Compose email

(view information, track,

and add templates,

knowledge base articles,

and sales literature)

Appointments and meetings

(view information and track)

Contacts

(view information and track)

Outlook 2016 (desktop client) O and M O and M1 O and M1 O3 and M2
Outlook 2013 (desktop client) O and M O and M1 O and M1
Outlook for Mac (desktop client) O and M
Outlook on the web (OWA) O and M O and M1 O and M1
Mobile Outlook app (4) O

(O)nline: Dynamics 365 (online), Exchange Online

(M)ixed: Dynamics 365 (online), Exchange Server 2013/2016

(1) Tracking email in compose mode and tracking appointments requires Exchange Server 2013 CU14 or Exchange Server 2016.

(2) Tracking contacts is supported only on Exchange Server 2016 CU3 and Outlook 2016 16.0.6741.1000 C2R version or later. Or, Outlook 2016 MSI version 16.0.4444.1000 or higher with the following KBs installed. For more information, see these KB articles:

(3) Supported only on Outlook 2016 16.0.7426.1049 or later.

(4) Supported on iPhones 6S or higher, with iOS 8 or higher.

 

Supported browsers for Outlook on the web (OWA)

You can use the Dynamics 365 App for Outlook with Outlook on the web on the following browsers:

  • Internet Explorer 11, or Microsoft Edge
    The following configuration is supported:
    • Protected Mode is enabled for Internet security zone. To enable Protected Mode: in IE 11, go to Tools > Internet options > Security tab > Internet.
    • Protected Mode is enabled for Local intranet security zone. To enable Protected Mode: in IE 11, go to Tools > Internet options > Security tab > Local Internet.
    • Your Dynamics 365 URL is in the Local intranet security zone list of trusted websites. In IE 11, go to Tools > Internet options > Security tab > Local intranet > Sites > Advanced.
  • Google Chrome (latest version) on Windows
  • Firefox (latest version) on Window
  • Apple Safari (version 9 or version 10) on Mac or on OSX

 

 

An important section to call out from the requirements link is the following section:

 

 

If you drill into this, you will find the following:

 

Internet Explorer 11 or later, which must be installed but doesn't have to be the default browser. To support Office Add-ins, the Office client that acts as host uses browser components that are part of Internet Explorer 11 or later.

 

What exactly does this mean? - This means that due to the Office Add-in dependency, the App for Outlook only renders in Internet Explorer 11.

 

If your organization is looking to update your JavaScript libraries and web resources in Dynamics 365 to start using the latest JavaScript language syntax (currently ECMA6), your custom JavaScript may fail through App for Outlook. A transpiler, such as Babel or Typescript, should be used to allow this to work with IE 11 through the App for Outlook.

 

 

Another important piece to call out from the supportability and requirements documentation is the following:

 

 

What does this mean? - The App for Outlook is not supported and will not work if Oauth is disabled in Exchange Online. OWA does not use Oauth, so you may see the App for Outlook connect there. However, if you try to connect from the Outlook desktop application, this will fail to connect to Exchange. In the diagram below, OfficeJS is what handles Oauth to Exchange Online. (Just a reminder, this blog series is focusing on Dynamics 365 Online/Exchange Online configuration)

 

Thanks for reading and stay tuned for part 3!

 

Aaron Richards

 

 

 

Dynamics 365 App for Outlook Part 3-Settings that affect tracking and correlation

$
0
0

For part 3 of the App for Outlook series, we are going to take a look at the settings that affect tracking.

 

Let's start at the organization level settings with System Settings. (We will not be covering folder-level tracking, as the App for Outlook is not required for this)

 

 

Configure email correlation

Use correlation to track email conversations - This only works with Server-Side Sync enabled and therefore, will work with the App for Outlook. With this box marked, hidden email properties are used to determine if the email should be correlated to an existing email conversation. If you use the EWS Editor for Dynamics 365, you could identify these as the ConversationIndex and In-Reply-To fields.

 

Use Tracking Token - This creates a tracking token in the Subject line of an email to help Dynamics 365 determine if the email should be tracked and is still recommended as the most accurate. Although, many organizations are not fond of the token being visible in the subject line. Unlike the legacy client, tracking an email with the App for Outlook prior to sending does not generate a tracking token. The tracking token is only generated when the email is sent directly from Dynamics 365. In this case, it would use the ConversationIndex. Another thing to be aware of is if someone modifies or removes the tracking token, correlation will break. Meaning that reply would not be tracked automatically.

 

Smart Matching - This is a correlation method from CRM 4.0.

Smart matching relies completely on the existence of similarity between emails. The subject and recipients (from, to, cc and bcc) list are the two important components that are considered with checking for similarity.

When an email is sent from Dynamics 365, there are two sets of hashes generated for it and stored in the database

Subject hashes:

To generate subject hashes, the subject of the email, which may include the Tracking token if its usage is enabled in system settings, is first checked for noise words like RE: FW: etc. The noise words are stripped off the subject and then tokenized. All the non empty tokens (words) are then hashed to generate subject hashes

Recipient hashes:

To generate the recipient hashes the recipient (from, to, cc, bcc) list is analyzed for unique email addresses. For each unique email address an address hash is generated.

Next when an incoming email is tracked (arrived) in Dynamics 365, the same method is followed to create the subject and recipient hashes.

To find the correlation between the incoming email and the outgoing email, the stored subject and recipient hashes are searched for matching values. Two emails are correlated if they have the same count of subject hashes and at least two matching recipient hashes.

Due to the possibility of emails being incorrectly correlated to the wrong message thread when the subject lines and recipients are similar, this is not my correlation method of choice. I recommend using either correlation(ConversationIndex) or Tracking Tokens instead and disabling Smart Matching.

 

Set tracking options for emails between Dynamics 365 users

Having this checked will create two separate email activities. One owned by the sender for the sent email and another for the received email that is owned by the recipient.

When this is not marked and an email is sent from a Dynamics 365 user as tracked to another Dynamics 365 user, the recipient will see this as tracked only for a short period and then tracking will be removed, as we are not tracking the incoming email.

There is another OrgDbOrgSetting (DoNotIgnoreInternalEmailToQueues) that also affects the way this functions. By default, the functionality is setup to cause queue-promoted items to ignore correlation and not create a received activity if the messageid matches another email (i.e. An email sent from Dynamics another Dynamics user or if the sent email is tracked into Dynamics before the queue attempts to promote the item or if a workflow rule sends an email message to a queue, email messages that are sent by the workflow rule are not delivered.)

The default setting is False, which gives you the outcomes above and internal email messages to queues will not be delivered.

If this is set to True, internal email messages to queues will be delivered.

 

Now, let's take a look at Personal Options, which are specific to each individual user

 

Allow Microsoft Dynamics 365 to send email on your behalf

This will allow Dynamics users to send email on your behalf. An example would be a delegate assistant for other users or a service account that is used in a workflow that sends emails. If the service account does not have this marked and the owner of the workflow is a different user, the workflow will fail.

 

Select the email messages to track in Microsoft Dynamics 365 (This is referred to as Email Filtering, as described in part one)

All email messages
This will track all email messages regardless no matter if it is a Dynamics 365 record or not. If you are using this setting and want the Sent folder to also track, you would need to enable the AutoTrackSentFolderItems OrgDbOrgSetting using this tool. Unless there is strict Exchange and Outlook governance, this setting may not be the best option, as it will promote items to Dynamics, whether they are related to Dynamics or not. It is important to note that when we promote items, these are only items in the default Inbox at the top-level of the information store. This means folders at the same level of the inbox, archive folders, etc.. will not be promoted.

Email messages in response to 365 email
This will track emails in response to current emails based on the correlation configuration in System Settings. It looks to see if this email has already been tracked in Dynamics 365, was an email that was generated and sent directly from Dynamics 365, or was automatically promoted in some manner with Server-Side Sync. This is the option I see used in most organizations.

Email messages from Dynamics 365 Leads, Contacts and Accounts
This will only track emails if the sender email address resolves to a Dynamics 365 lead, contact, or account. If this resolves to one of the above record types, the email will be tracked automatically, even if it is not tied to a previously tracked email.

Email messages from Dynamics 365 records that are email enabled
This will track emails from all record types, including custom record types that contain an email address field. If this resolves to one of the above record types, the email will be tracked automatically, even if it is not tied to a previously tracked email.

When Dynamics 365 does email resolution or association, it looks specifically at the email address field of the entity. This must be a Single Line of Text field with Email format. Any time a field as described above is added to a record, this creates a record in the EmailSearchBase SQL table, which is queried to identify if and what record the email address resolves to. Email filtering, correlation, and resolution will also be discussed in scenarios in part 4 of this series

Since this is a user controlled setting, an administrator can view and update these settings for all users with XRMToolbox.

Automatically create records in Microsoft Dynamics 365

This will automatically create a Contact or Lead in Dynamics 365 using the Sender or Organizer email address of tracked e-mails if the Contact or Lead does not already exist. There is also an OrgDbOrgSetting to control the organization's ability to create contacts automatically. If you set, AutoCreateContactOnPromote to False, it will prevent automatic contact creation regardless if the personal option is marked to do so or not.

Thanks for reading! Part 4 coming soon...

 

Aaron Richards

Dynamics 365 App for Outlook Part 4-Working with Emails

$
0
0

Welcome back to part 4 of the Dynamics 365 App for Outlook series. In this post, we are going focus on more specific email tracking scenarios. In the following days, we will break down appointments and contacts.

 

The first area that needs some attention is automatic email tracking.

In the last post, we went through the email filtering settings in a user's personal options. If a user's personal options (email filtering) are set to track all emails, this will track all email messages regardless, no matter if it is a Dynamics 365 record or not. However, the Sent folder is not tracked by default. If you are using this setting and want the Sent folder to also track, you would need to enable the AutoTrackSentFolderItems OrgDbOrgSetting using this tool.

 

Unless there is strict Exchange and Outlook governance for what users can and cannot store in Outlook, this setting may not be the best option. It will promote all items to Dynamics, whether they are related to Dynamics or not. In most cases, I see this used only for troubleshooting to ensure emails are promoted into Dynamics and not in live production environments unless emails are governed appropriately. Yes, this means a personal email could be promoted into Dynamics.

 

In most cases, the setting Email messages in response to 365 email is used. It is also the default setting. However, it is best to evaluate each option to determine what is best for your organization.

 

Since this is a user controlled setting, an administrator can view and update this using the User Settings Utility within XRMToolbox.

 

How are emails, replies or forwards, tracked that are part of a conversation, that I may not want tracked in Dynamics 365?

 

Example A:

      1. User A sends an email to multiple recipients, including contacts and other Dynamics users
      2. User B replies to this thread
      3. Contact A also replies to this thread
      4. User B replies to the thread, but removes Contact A as a recipient
      5. They do not want this reply automatically tracked

 

In this case, it will automatically track because it identifies the ConversationIndex and In-Reply-To values as an email that is part of a thread.

 

To have this email untracked, the user would have to manually untrack the reply with the App for Outlook as well as any replies to this because the master email is still tracked.

 

 

Example B:

      1. User A sends an email to multiple recipients, including contacts and other Dynamics users
      2. User B forwards this thread to another user for internal conversation
      3. They do not want the information in this forward automatically tracked

 

In this case, it will automatically track because it identifies the ConversationIndex and In-Reply-To values as an email that is part of a thread.

 

To have this email untracked, the user would have to manually untrack the forward with the App for Outlook as well as any replies to this because the master email is still tracked.

 

Example C:

      1. User A sends an email to multiple recipients, including contacts and other Dynamics users
      2. User B forwards this thread to another user for internal conversation AND changes the subject
      3. They do not want this forward or replies automatically tracked

 

In this case, it will automatically track because it identifies the ConversationIndex and In-Reply-To values as an email that is part of a thread.

 

To have this email untracked, the user would have to manually untrack the forward with the App for Outlook as well as any replies to this because the master email is still tracked.

 

 

 

If you untrack a reply or forward to a thread on an email, and if the initial/master email is still tracked, it will continue to track replies. If there are certain replies you do not want to track, you will need to untrack these manually.

 

 

There was a setting used in the previous Outlook Client to prevent automatic tracking of Replies and Forwards, however this does not work with the App for Outlook because the actual tracking is done by Server Side Sync. There is a product suggestion that would be helpful here to create a NONE option for automatic tracking. If this setting were made to work with the App for Outlook, it would require manually tracking any replies or forwards you would like promoted to Dynamics. There is a product enhancement suggestion available here. Whichever way you look at it, there will be manual tracking or untracking of these replies and emails.

 

 

When resolving recipient email addresses to records in Dynamics, if there is more than one record in Dynamics with the same email address, which record is it resolved to?

 

It resolves using the method below:

If there are duplicate records within Dynamics 365 with the same email address, the contents of the email From field will resolve to the first active record in the following order on an incoming email:

      1. SystemUser- should always be first
      2. Contact
      3. Account
      4. Lead
      5. Equipment
      6. Team
      7. Business unit
      8. Email-enabled entities (for example: Queues, custom, etc.)

 

Emails will not resolve to inactive User records in the From field. There is a setting to resolve to other inactive entity records but this does not include Users: ResolveForInactiveEntities

 

Here are some additional points on how it resolves recipient records in the To or CC field of an incoming email:

If there is an inactive user in the recipients line, the App for Outlook may show that the user matches the email, but when you track, the promotion will not resolve to that email for the inactive user and it will show up in red as unresolved. It will not resolve to inactive users regardless of the ResolveForInactiveEntities setting.

 

 

 

 

If the email address is tied to an active user, it will display that in the App recipients pane, but it will still resolve to each active Dynamics record with that email address once it is promoted. If the ResolveForInactiveEntities setting is True, it will also resolve to inactive entity records except Users.

 

The App for Outlook will only show one of these records in the recipients pane, but in Dynamics, it will resolve to all records with that email address on incoming emails as long as Set To,cc,bcc fields to unresolved values if multiple matches are found is set to No in System Settings

 

 

Here are some additional points on how the To or CC field resolves on a tracked sent item:

 

If the user is active and there is a contact, it will resolve to both records, although it will show resolved to the user in the App for Outlook. It will resolve to all active records that match that email address or also inactive records if you have enabled ResolveForInactiveEntities. Again, this does not include users. You can see below it resolves to an Account, User, Contact and Lead.

If the User is Inactive, it may appear that the record is found/resolved in the App, however, when the item promotes into Dynamics, it will show up as unresolved.

 

One important thing to mention here is that this does NOT resolve to records only in the default email address fields. If you have a custom Single Line of Text field with Email format on a Contact record, you may see some interesting results.

 

For example:

      • Bob Jones is a user inside Dynamics, and on the User form, the email data field of “Primary Email” has the value Bob@test.com
      • There is an Opportunity record named “BobOpp” with the email data field of “Email” set to Bob@test.com
      • There is a Case record named “BobCase” with the email data field of “Email” set to Bob@test.com
      • There is a Contact record named “Leslie Baker” set to primary email of Baker@test.com with the email data field of “Contact Approver” set to Bob@test.com
      • There is another Contact record named “Greg Marcus” set to primary email of Marcus@test.com with the email data field of “Contact Approver” set to Bob@test.com
      • There is another Contact record named “Happy Hogan” set to primary email of Hogan@test.com with the email data field of “Contact Approver” set to Bob@test.com
      • The System Setting of “Set To,cc,bcc fields as unresolved values if multiple matches are found in Incoming Emails” is set to No
      • There is an email in Bob’s mailbox where Bob@test.com is on the To: and CC: line

If this email is promoted into Dynamics due to Bob tracking the email through Dynamics App for Outlook (as an example), the promoted email in Dynamics will show the following values:

To: Bob Jones; BobOpp; BobCase; Leslie Baker; Greg Marcus; Happy Hogan

CC: Bob Jones; BobOpp; BobCase; Leslie Baker; Greg Marcus; Happy Hogan

In the screenshots below you can see this example with only the contact records. (disregard my name in the To line. I sent to myself to track the item to demonstrate correlation)

 

 

Can I remove the option for users to Track without Regarding, so they are forced to Set Regarding to a record in Dynamics?

No, you cannot force users to Set Regarding on an email or appointment instead of allowing them the ability to Track Without Regarding. If you are migrating from the legacy Outlook client, you may have been using an OrgDbOrgSetting (OverrideTrackInCrmBehaviour) that did allow this functionality. This setting is not honored by the App for Outlook.

 

 

 

What happens if I receive a reply to a previously tracked email and choose to reply back before it is tracked. (This is not immediate tracking, so it waits for the async service to pick it up for tracking)

Replying to emails before it is tracked will still track during the next sync cycle. If you have been using the legacy Outlook client for years, this scenario was different, where a response to a previous reply that is not yet tracked would not be tracked. So that is no longer an issue if you had encountered this in the past. It will still track.

 

However, this can still be confusing for users where they may think that since they are responding to a reply that does not show up yet as tracked, that their reply will not be tracked either. Here is a break out:

      1. User A sends Tracked email to User B.
      2. User B received email, but it does not show as tracked yet in their inbox (due to asynchronous processing).
      3. User B replies (they could also forward) the message with sensitive information that should not reside in Dynamics 365. Now that message will end up in Dynamics 365 with the sensitive information.

Synchronous tracking would help this situation, but at the time of this post, that is not how emails are promoted/tracked into Dynamics. Something to be aware of.

 

 

How can I tell from Outlook if an email or appointment is tracked in Dynamics?

      • If you are familiar with the legacy Outlook client, there was an icon that appeared on tracked items, making it easy to determine if the record was tracked. Unfortunately, with the App for Outlook, there is no icon to show if it is tracked.

 

What you can do for emails, is pin the App. This will stay pinned as you navigate through emails. However, this does not work for appointments.

 

The other option is to use Category Tracking. I will not be going into this during this blog series. We may be looking at this in a future post. However, be sure you test this feature thoroughly to ensure it works for your needs.

 

When I open the App for Outlook, I see the message, "Create contacts first to avoid duplicates." Can I disable this?

No. This is not configurable and will appear when the sender of the email is unknown (does not resolve to a Dynamics record)

 

Which emails are tracked immediately vs. asynchronously?

 

At the time of this post, this is the most recent functionality

 

Use Case Initial Promotion Method Fallback Promotion Method
Email without attachments in read mode for the first time Immediate Async
Recipient tracks a previously untracked email Async Async
Track an email in compose mode Async Async
Track an email with attachments Immediate Async

 

 

How are tracked Email deletions handled?

 

Email deletions in Dynamics 365

      • Deleting an email message in Microsoft Dynamics 365 does not delete the tracked message from Outlook/Exchange.

 

Email deletions in Outlook

      • Deleting a tracked email message in Outlook does not delete the email message from Microsoft Dynamics 365.
      • If you stop tracking an email message in Outlook, the App for Outlook asks whether you want to delete the email message in Microsoft Dynamics 365.

 

Thank you!

 

Aaron Richards

Dynamics 365 App for Outlook Part 5-Working with Appointments

$
0
0

Part 1 | Part 2 | Part 3 | Part 4

For part 5 of the Dynamics 365 App for Outlook series, we are going focus on specific appointment tracking scenarios. In the following post, we will break down contacts.

Let's get into it…

If I receive a meeting request, can I track this into Dynamics 365?

You cannot track a meeting request. You will receive the message below from the email list view:

 

 

Or if you open the meeting invite item, you will see the App is grayed out.

 

You also cannot track meeting replies (a reply that states someone accepted your meeting request).

 

 

However if you accept the meeting request, you can track the appointment only if this was sent from a Non-Dynamics user such as a Contact or an external email. See below:

 

 

Can I track an appointment sent to me from another Dynamics User?

No, if this was sent from another Dynamics 365 user, you will not be able to track this appointment and you will receive the following message instead of the tracking options. There is a setting that affects how this works. I will be updating this blog post for this scenario specifically in the coming weeks.

 

When I create an appointment with attendees and send the meeting request, is this tracked and does it reflect as tracked on the Appointment shown in my calendar?

When I create a new appointment in Outlook with required attendees, it sends a meeting request but also creates an appointment on your calendar. When creating an appointment, before I send it (compose mode), I can open the App for Outlook and track it.

 

 

After it is sent, the meeting request that exists in your sent items does not actually show as tracked.

 

But the appointment on your calendar does

 

 

What happens when I change the date or start and end times of an appointment in Outlook that is synchronized to Dynamics?

This will reflect the changes in Dynamics. If this has meeting recipients, they will also receive an update to the original meeting as you would expect with normal Outlook functionality. You can actually move the dates ahead to a future date or if it is a meeting that already occurred, you can move it backwards. You will want to review the bottom of this post for how we synchronize historical appointments.

 

When resolving recipient email addresses to records in Dynamics, if there is more than one record in Dynamics with the same email address, which record is it resolved to?

It resolves using the method below:

If there are duplicate records within Dynamics 365 with the same email address, the contents of the appointment From field will resolve to the first active record in the following order on an appointment:

a. SystemUser- should always be first
b. Contact
c. Account
d. Lead
e. Equipment
f. Team
g. Business unit
h. Email-enabled entities (for example: Queues, custom, etc.)

Appointment recipients will not resolve to inactive User records in the From field. There is a setting to resolve to other inactive entity records but this does not include inactive Users: ResolveForInactiveEntities

 

Here are some additional points on how it resolves recipient email addresses in the To or CC field of an appointment:

If there is an inactive user in the recipients line, the App for Outlook may show that the user matches the email address, but when you track, the promotion will not resolve to that email for the inactive user and it will show up in red as unresolved. It will not resolve to inactive users regardless of the ResolveForInactiveEntities setting.

 

If the email address is tied to an active user, it will display that in the App for Outlook recipients pane, but it will still resolve to each active Dynamics record with that email address once it is promoted, as long as Set To,cc,bcc fields to unresolved values if multiple matches are found is set to No in System Settings. If this is set to yes, they will show as unresolved. Also, if the ResolveForInactiveEntities setting is True, it will resolve to inactive entity records except inactive Users.

 

One important thing to mention here is that the emails addresses on the appointment do NOT resolve to records only in the default email address fields within Dynamics. If you have a custom Single Line of Text field with Email format on a Contact record, you may see some interesting results. (Additional screenshots are available in Part 4- working with Emails)

For example

  • Bob Jones is a user inside Dynamics, and on the User form, the email data field of “Primary Email” has the value Bob@test.com
  • There is an Opportunity record named “BobOpp” with the email data field of “Email” set to Bob@test.com
  • There is a Case record named “BobCase” with the email data field of “Email” set to Bob@test.com
  • There is a Contact record named “Leslie Baker” set to primary email of Baker@test.com with the email data field of “Contact Approver” set to Bob@test.com
  • There is another Contact record named “Greg Marcus” set to primary email of Marcus@test.com with the email data field of “Contact Approver” set to Bob@test.com
  • There is another Contact record named “Happy Hogan” set to primary email of Hogan@test.com with the email data field of “Contact Approver” set to Bob@test.com
  • The System Setting of “Set To,cc,bcc fields as unresolved values if multiple matches are found in Incoming Emails” is set to No
  • There is an appointment on Bob’s calendar where Bob@test.com is a recipient on the To: and CC: line

If this appointment is promoted into Dynamics through the Dynamics App for Outlook (as an example), the promoted appointment in Dynamics will show the following values:

To: Bob Jones; BobOpp; BobCase; Leslie Baker; Greg Marcus; Happy Hogan

CC: Bob Jones; BobOpp; BobCase; Leslie Baker; Greg Marcus; Happy Hogan

How can I tell from Outlook if an appointment is tracked in Dynamics?

As mentioned in the last post, if you are familiar with the legacy Outlook client, there was an icon that appeared on tracked items, making it easy to determine if the record was tracked. Unfortunately, with the App for Outlook, there is no icon to show if it is tracked. Additionally, there is no option to pin the App on Appointments. You can see below that the icon to pin the App is missing.

 

You would need to use Category Tracking, which shows a specified category for Tracked in Dynamics 365. I will not be going into this during this blog series. We may be looking at this in a future post. However, be sure you test this feature thoroughly to ensure it works for your needs.

 

 

What happens when I untrack an Appointment from Outlook?

If you untrack an appointment, you will get the option to untrack or remove the link to the record. If you own the appointment record, you will also get the option to delete the appointment

 

How do we synchronize historical appointments?

This is likely one of the most common questions I encounter.

Appointments in the past: You can still track a past appointment that already exists in Outlook into Dynamics 365, which will create the appointment record in Dynamics, but Dynamics 365 doesn’t synchronize changes on these past appointments or send historical meeting invites.

However, if you are also creating a historical appointment in Outlook prior to tracking into Dynamics, Outlook will still send a meeting request. This will happen with standard Outlook functionality regardless of if the App for Outlook is used or not.

Recurring appointments: In Outlook, a series of appointments can have no end time, but in Dynamics 365, instances as part of the recurring appointment will be created if the instance is either within the near future (12 months), or was modified as an exception of the series.

Service activities and service appointments: You can push service appointments in Dynamics 365 to Outlook as a regular appointment, but the appointment in Outlook won’t sync back to Dynamics 365, and you should always modify the service appointment in Dynamics 365 to provide consistency. Directly updating the appointment in Outlook is not allowed nor recommended.

 

Which appointments are tracked immediately vs. asynchronously?

At the time of this post, this is the most recent functionality

 

Use Case Initial Promotion Method Fallback Promotion Method
Recipient tracks an appointment in read mode for the first time Immediate Async
Recipient tracks a previously untracked appointment Async Async
Track an appointment in compose mode Async Async
Organizer tracks an appointment Async Async
Track an appointment in compose mode Async Async

 

Our business has requirements to display the appointment form differently for different business units. Why don’t I see the option to create a new appointment form in Dynamics?

It is a current design that we have only one appointment form due to the tight integration with the fields required by Exchange and Outlook. This has been brought up many times and there is a Product Enhancement Suggestion here.

 

How are tracked Appointment deletions handled?

Appointment deletions in Dynamics 365

  • Deleting a tracked appointment in Microsoft Dynamics 365 deletes the appointment in Outlook if the following is true:
    • The appointment is current.
    • You are the owner or organizer of the appointment record.

 

Appointment deletions in Outlook

  • Deleting a tracked appointment in Outlook deletes the appointment in Microsoft Dynamics 365.
  • If you stop tracking an appointment, App for Outlook asks whether you want to delete the appointment from Microsoft Dynamics 365. The appointment record is deleted in Microsoft Dynamics App if the following is true:
    • The appointment is current.
    • You are the owner of the appointment record.

 

Stay tuned next week for the rest of this series!

 

Aaron Richards

Part 1 | Part 2 | Part 3 | Part 4

Dynamics 365 App for Outlook Part 6-Working with Contacts

$
0
0

Finally, we are going to take a closer look at working with Contacts through the App for Outlook.

Where do I find the Dynamics 365 App for Outlook for Contacts?

The contact view shows up differently than the App appears on Emails or Appointments. It must be accessed through the Add-in, accessible at the bottom of the Navigation

 

Note: You cannot create a new Contact from this view.

 

Can I add custom columns to the Contacts view?

You can select new columns to add to the view, however, you cannot yet modify the columns that are available in this list:

 

Tracking and linking Contacts

The options in the screenshot below are useful when you have a Contact record selected within the view:

 

 

- This will allow you to track or promote the Contact into Dynamics. You can do this for one or multiple contacts at one time.

 

 

- This will allow you to untrack a Contact. You can do this for one or multiple contacts at one time.

 

- This allows you to track and link the Contact to a Parent Account. You can also link a Tracked contact by selecting the record and clicking the link icon. Yes, you can also link multiple contacts to the same account at one time, but this must be to the same account.

 

 

 

- This will open a new Outlook email and will populate the recipient with the email address of the Contact automatically. You can select multiple contacts at once to do this as well and all selected contact email addresses will be added to the recipients of the email. If there is no email for the contact, it will show up as undefined.

 

- This will open a new Outlook appointment and will populate the recipient with the email address of the Contact automatically. You can select multiple contacts at once to do this as well and all selected contact email addresses will be added to the recipients of the appointment. If there is no email for the contact, it will show up as undefined.

 

When I search in the view, why does it only return 5,000 records, although in Dynamics, we can see there are more records?

 

There is currently a 5,000 record count limit

 

Also in regards to searching contacts, you cannot search for data within the Tracking Status, Business Phone, or Email fields.

 

 

Why don’t I see the add-in available in OWA to track contacts?

Tracking Contacts only works in Outlook 2016 desktop and up only. Contact tracking does not work in OWA. Refer to the this link.

 

 

Let's not forget that unresolved recipient or sender email addresses can be created as Contacts from the App within an email or appointment as well

This can be done manually or using the Automatically create records in Microsoft Dynamics 365 setting in your Personal Options. To recap this setting:

 

This will automatically create a Contact or Lead in Dynamics 365 using the Sender or Organizer email address of tracked e-mails if the Contact or Lead does not already exist. There is also an OrgDbOrgSetting to control the organization's ability to create contacts automatically. If you set, AutoCreateContactOnPromote to False, it will prevent automatic contact creation regardless if the personal option is marked to do so or not.

 

If you choose to do this manually, you will see this option:

 

 

 

 

Make sure you proactively work to minimize duplicate contacts

A very important part of tracking contacts from Outlook into Dynamics is preventing duplicates with duplicate detection rules and ensuring that synchronization filters are configured properly. You can also create system level sync filters using the SDK or the Sync Filter Manager. There are a ton of great articles out there on creating duplicate detection rules using the out of box functionality as well as custom add-ons. Be sure to evaluate these in great detail and ensure that you have them enabled prior to importing or, in this case, tracking contacts in from Outlook. There is a great chance that the same contact exists within multiple user address books.

 

Let's look at this scenario: Two Dynamics users have the same contact in their Outlook address book. In Dynamics, Contacts are owned by Teams and not Users.

 

This is the default Contact synchronization filter criteria:

 

If your contacts are owned by Teams, this filter would not work for you. You would need something similar to the following:

User B has the contacts highlighted in their Outlook address book. They do not exist in Dynamics.

 

User A also has these users in their Outlook address book and tracks these into Dynamics. There are no duplicate in Dynamics, as User A is the only user to track these to Dynamics.

They are assigned to the team for which both users are a member of within Dynamics.

 

Due to the sync filters, these sync down to the other user's Outlook as tracked. This is a common scenario where someone may see duplicates in Outlook if they have team ownership. In this case, you would see one set of tracked and the other not tracked.

 

Although with the Dynamics 365 App for Outlook, these only appear under the add-in section and not the default store for Contacts within Outlook. You can see the default Contacts location in Outlook below still shows only the three original contacts and not the duplicates brought down from Dynamics.

 

 

 

How are tracked Contact deletions handled?

 

Contact Deletions in Dynamics 365

  • If you are not the owner of the contact record, deleting a contact from Microsoft Dynamics 365 deletes the tracked contact from Outlook.
  • If you are the owner of the contact record, deleting a contact from Microsoft Dynamics 365 does not delete the contact from Outlook.

 

Contact Deletions in Outlook

  • Deleting a tracked contact in Outlook does not delete the contact record from Microsoft Dynamics 365.
  • If you are the owner of the contact record, and you stop tracking the contact, 365 for Outlook asks whether you want to delete the contact record from Microsoft Dynamics 365.
  • If you are not the owner of the contact record and you stop tracking the contact, Microsoft Dynamics 365 deletes the contact record.

 

Check out the rest of the series below:

Part 1 | Part 2 | Part 3 | Part 4 | Part 5

 

Thank you for reading!

Aaron Richards

 

Dynamics 365 App for Outlook Part 7-Helpful tips for using the App

$
0
0

Welcome to part 7 of the App for Outlook blog series. In this post, we are going to go over a couple helpful tips when using the App for Outlook.

 

Create a Set Regarding record on the fly and automatically track to that record

If you need to create a new record, such as an Account that you also want to Set Regarding to, you can do this with the following steps.

 

1. Click the Set Regarding search bar:

 

 

2. Then, click the Search icon in the Set Regarding pane:

 

 

 

3. You will need to select the entity to enable the +New button (It will be grayed out until narrowed down to a specific entity). In this case, Accounts:

 

 

4. Fill out your record details and click Save:

 

 

5. Once you click Save, it will automatically Set Regarding to that record for the email or appointment record you are working in:

 

 

 

 

What record should I Set Regarding to?

I cannot tell you specifically what record to Set Regarding to. However, I can tell you that if a tracked email or Appointment has recipients that already resolve to Contacts in Dynamics, the email will already show up as an activity on the timeline for that Contact, as well as the Activities views for the Users that tracked or were resolved as a recipient. In this case, using Set Regarding would be better used to correlate this email to a specific record that the email is referencing (i.e. a specific Account, project, proposal, Contract, Deal, Opportunity, etc…) You would then be able to see this on the Contact and Account, or whichever record you Set Regarding to.

 

 

 

Accessing Views

To easily access views from the App for Outlook, you can click on this icon and select the most recently used icon, as shown below.

Once you are here, you can pin favorite records and views for easy access:

 

 

 

 

Modify the sitemap of the App for Outlook app to access entities directly.

 

1. Open the Dynamics 365 App for Outlook app in App Designer:

 

 

2. Click to modify the Site Map:

 

 

3. Add a new Area, Group, or Subarea to the Site Map. In this case, we are testing with a Subarea:

 

 

4. Click to edit the Subarea properties:

5. Select the type of Entity and Contact as the Entity:

 

 

6. Publish the Site Map:

 

 

7. Now, open the Dynamics 365 App for Outlook and from the Site Map, you can access the Contact entity directly:

 

 

Check out the rest of the series below:

Part 1 | Part 2 | Part 3 | Part 4 | Part 5 | Part 6

 

Thank you for reading!

Aaron Richards

 

Podcast and Overview: Microsoft Dynamics 365 (on-premises) Update 2.3

$
0
0

We're proud to announce that all packages for Microsoft Dynamics 365 (on-premises) Update 2.3 were released December 1st, 2018 to the Microsoft Download Center and are available for download! Appropriate packages will appear on Microsoft Update shortly.

Note: The Updates documented in this blog update the Dynamics CRM/365 Customer Engagement components described in this Microsoft Knowledge base article:

Microsoft Dynamics CRM Installations, Updates and Documentation

Note the naming convention change! For more details, see the Dynamics CRM Product Group blog "New naming conventions for Microsoft Dynamics CRM updates"

Microsoft Dynamics 365 (on-premises) Update 2.3 Build number:

8.2.3.0003

Microsoft Dynamics 365 Update 2.3 Microsoft Download Center page

Here's the "Master" Microsoft Dynamics Knowledge Base article for Microsoft Dynamics 365 (on-premises) Update 2.3: (KB 4467675). Going forward, the plan is to continue publishing Master Knowledge Base articles for CRM Updates a bit in advance of release to aid planning.

Go to Top

The "Microsoft Dynamics CRM / Dynamics 365 Updates: Release Dates, Build Numbers, and Collateral" Page

For pointers to download locations, release dates, build information, and CRM Premier Field Engineering blogs and podcasts for all supported Microsoft Dynamics CRM Updates, Update Rollups, and Service Packs, visit the "Microsoft Dynamics CRM / Dynamics 365 Updates: Release Dates, Build Numbers, and Collateral" page.

Go to Top

Microsoft Dynamics 365 (on-premises) Update 2.3 Prerequisites:

  • Essentially the prerequisites listed in the Microsoft Dynamics CRM 2016 Implementation Guide download or Online TechNet for the various CRM components serviced.

Go to Top

Fixes released via Microsoft Dynamics 365 (on-premises) Update 2.3:

Performance Improvements

The following list details issues whose resolutions improve the speed or functionality of Dynamics.

  • Incremental system-wide performance improvements have been made in this update.

Unexpected Behavior

The following list details issues whose resolutions correct actions performed in Dynamics that do not work as intended.

  • In entitlements with empty Remaining Terms and Remaining Terms values, the Remaining Terms failed to update when saved.

Repaired Functionality

The following list details issues whose resolutions repair items in Dynamics that are not functioning.

  • Emails auto-promoted unintentionally when some users received an email with a queue that was set to promote all incoming email.
  • In a case, users could not use the "Similar Cases" field when the field was already used more than once and the second occurrence of the field was then selected.
  • Tasks were being automatically deleted or completed without manual intervention.
  • Users could not rename the "Case" button label.
  • SLAs created on non-working days (such as weekends and holidays) started immediately instead of not considering the non-working time.
  • Alert page would not load in users' mailboxes.
  • The ribbon menu was displaying even when the appointment was set to "Read-only" status.

Error Messages, Exceptions, and Failures

The following list details issues whose resolutions correct actions that produce errors, unhandled exceptions, or system or component failures.

  • An error occurred when attempting to show Activity Feeds.
  • An error occurred when attempting to send emails with attachments.
  • An error occurred when selecting the "Remove Selected Subject" button.
  • An error occurred when attempting to run a test with the JavaScript Dom Benchmark diagnostic tool.

Go to Top


Dynamics 365 App for Outlook Part 8-Email Governance

$
0
0

For part 8 of this blog series, I want to talk a little bit about Email governance in Dynamics 365. This is not specific to the App for Outlook, however, with tracking and promoting Outlook data into Dynamics 365 comes additional consideration around security of who should see the tracked data. I will not be going in depth to the solutions, but providing a high-level overview of options I have encountered. If you are using or have seen something different, feel free to share in the comments section.

 

The business and security requirements should always be reviewed within your organization so that you can assess all available options. The options around email governance are not limited to this list, however, these are some of the scenarios I have seen tested or put in place to assist with meeting different business requirements.

 

What options do I have for Email Governance to restrict or filter email information from being seen within Dynamics?

 

In most cases I have seen, this is tied to the content of the email or appointment, but sometimes extends to the attendees of a meeting as well.

 

The first option that should be evaluated is using the standard security structure within Dynamics, using business units, security roles, teams and sharing. This includes Owner Teams, Access Teams, and cascading shares through relationships. Hierarchy security is another option that should be considered. This could be based on Managers or Positions. Remember that team access and sharing can also be done programmatically, so this can become considerably complex if the requirements call for it.

 

 

The second option, which is still part of basic out-of-box functionality is Field Level Security. In this case, enabling Field Level Security on the Description field. By creating a field security profile for this field, you can specify which users can see or edit the data. If they are not added to a profile, the data will be masked completely and it will not be accessible through reports or Advanced Find. However, this does not change visibility on the Exchange/Outlook side

 

Field Security is enabled on the field definition:

 

 

In the Field Security Profile, you must add a user to the profile and give them access to Read the field. The default is No.

 

 

The Description field of the email would appear masked for users that do not have Read access, as you see below:

 

The data is not available through Advanced Find either:

 

 

As a user with the System Administrator role or a user that has been given Read access, you would see the following:

 

 

 

 

The third option is using workflows. You could use a simple workflow to remove the body of the email on incoming emails. You could also do this for Sent emails, but the logic in the workflow would have to be different, so it is cleared after it is sent.

I have also seen a custom workflow used to archive the email data in a separate entity that is only accessible by administrators or a group of users specified. In this case, a workflow would copy the email body from the original email to a new record and field in a custom entity, and then would delete the Description content on the original email. You may also need to copy other data on the email to correlate back for any audit purposes. This process does not remove the body of the email in Outlook.

 

The email in Dynamics would appear with a blank Description field like below:

 

 

 

I would not recommend doing this for appointments due to multiple moving pieces with synchronization. Many will use Field Security or other features such as a related appointment notes entity restricted with security.

 

The fourth option also includes using a workflow along with a custom sensitivity field and business rules. You would create a sensitivity field on the email or appointment form with values that match the business needs and requires. Based on the values selected, use a workflow, business rule, or JavaScript to display, hide, remove content as needed

 

Another example, is where there may be scenarios where the content can only be visible to specific users based on who is in the To or From lines (sender and recipients).

 

For this, one could use JavaScript to validate the sender and recipients and determine the fields to hide.

 

A more simple way to do this is to:

  1. Create a workflow that validates the sender or recipients and incoming direction
  2. If it meets certain criteria, change the email status to draft
  3. Copy the email description field into a separate field that is Field Security enabled
  4. Then clear the content of the default description field
  5. Flip a custom flag on the record and use a business rule to show the new field and hide the old field if that flag is marked

 

The only issue with this is when you copy from the description field on an email, it will copy all of the HTML tags along with it. So a custom workflow would have to be used here to strip out the HTML characters.

 

An example of a workflow, without removing the HTML characters would look like below.

 

Here, we check the Sender and if it matches a certain user or contact and it is an incoming email, then we change the status to draft, update the email and change the status back to Received.

 

Here is the update of the email, where we set the Sensitivity, copy the Description value to the new Field Security Enabled field, and clear the default Description field.

 

 

 

This is the outcome without using a business rule to hide the original description field. You can see the characters that would need to be stripped out, as highlighted below:

 

 

Again, these are just some options I have seen put in place to get you thinking of the different ways you can control email visibility within Dynamics.

 

Check out the rest of the series below:

Part 1 | Part 2 | Part 3 | Part 4 | Part 5 | Part 6 | Part 7

 

Thank you for reading!

Aaron Richards

 

Dynamics CRM Reports complaining Reporting extension(SRS Data Connector) is not installed

$
0
0

Hey all-

I am starting a series of re-posts from my personal blog site. Recently, I decided not to maintain separate personal blog site and now my personal blog site is offline. Here is the first one...

-------re-post----------

Here I am talking about an interesting issue while running Dynamics CRM Reports. When I faced this for first time it felt rare corner scenario but recently I worked with a couple of more customers who ran into same issue. This type of strange issues can take good amount of time to investigate/troubleshoot so worth sharing.

Running any CRM report fails with error stating Reporting Extensions (Data Connector) is not installed. Of course Reporting Extensions (Data Connector) is installed and in fact it’s been removed and reinstalled in attempt to fix the issue, but no difference in error. Below is how error reads/looks like:

Reporting Error

Reports cannot be run because the Connector for Microsoft SQL Server Reporting Services, a required component for reporting is not installed on the server that is running Microsoft SQL Server Reporting Services.

 

Looking deeper, SSRS Event logs reports failure loading CRM extension.

Log Name:      Application
Source:        Report Server (MSSQLSERVER)
Date:          7/10/2015 3:11:55 PM
Event ID:      108
Task Category: Extension
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      SSRSBox
Description:
Report Server (MSSQLSERVER) cannot load the MSCRM extension.

Same event log error is there for other Report Server extensions as well. MSCRMFETCH, SQLPDW, TERADATA are other exception those fail to load within SSRS.

Report Server Service log file also complains about not being able to load the file or missing files.

extensionfactory!ReportServer_0-1!9f8!07/08/2015-02:28:31:: e ERROR: Exception caught instantiating MSCRMFETCH report server extension: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.DllNotFoundException: Unable to load DLL 'SRSDataConnectorBootstrapper.dll': The specified module could not be found. (Exception from HRESULT: 0x8007007E)
 at Microsoft.Crm.Reporting.DataExtensionShim.Common.NativeMethods.CreateManagedObject(String fullAssemblyPath, String assemblyName, String typeName, Object& obj)

extensionfactory!ReportServer_0-1!9f8!07/08/2015-02:28:31:: e ERROR: Exception caught instantiating TERADATA report server extension: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.IO.FileNotFoundException: Could not load file or assembly 'Teradata.Client.Provider, Version=12.0.0.0, Culture=neutral, PublicKeyToken=76b417ee2e04956c' or one of its dependencies. The system cannot find the file specified.
File name: 'Teradata.Client.Provider, Version=12.0.0.0, Culture=neutral, PublicKeyToken=76b417ee2e04956c'

All the files being reported in above exceptions were present on expected path and Report Server service account was given adequate permissions. ProcMon comes to mind as handy tool for investigating file access issues. After good analysis of working and non-working logs could nail it down to VC++ runtime dlls missing or being wrong versions on non-working environment. VC++ runtime is a required component for SSRS extensions to load and function properly.

Once we knew its VC++ runtime fix was relatively easy and quick. Either replace the corrupt or missing file with appropriate version from working environment or remove and reinstall Visual C++ Redistributable Package from Microsoft download page. The Visual C++ Redistributable Packages that ships in Redist folder of Dynamics CRM installation media can also be used.

The file msvcr100.dll in C:\Windows\System32 folder was missing in one of the environment, just placing this file from a working environment resolved the issue. After correcting missing/wrong file or reinstalling VC++ runtime, restarting SSRS, IIS on CRM server and clearing IE cache resolves the errors loading SSRS extensions and CRM Reports render w/o any issues.

 

Hope this helps! Cheers!

Bhavesh Shastri

Dynamics 365 Monthly Update-December 2018

$
0
0
Quick Links: Featured News | Updates and Releases | Additional News | Training Corner

Featured News


Get started with Dynamics 365 Service Scheduling

The new scheduling experience in Customer Service Hub is now live. Powered by Universal Resource Scheduling, this experience provides an efficient way to schedule resources for service activities. It considers the availability of employees, facilities, and equipment to plan schedules accordingly. It also helps customer service organizations improve service quality by preventing over-scheduling.

Review this post on the Dynamics 365 Customer Engagement Team Blog for more information and instructions on how to install the feature.


Microsoft Ignite | The Tour

Introducing a new global 17-city event designed to bring the best content from Microsoft Ignite directly to technical practitioners worldwide – ensuring they get the most out of Azure, Microsoft 365, Dynamics 365, and the Power platform. With 100+ deep-dive sessions and workshops, attendees will explore the latest developer tools, cloud technologies, and learn how to put their skills to work in new areas.

Upcoming stops on the tour include:

  • Toronto: January 10-11, 2019
  • Singapore: January 16-17, 2019
  • Washington, DC: February 4-5, 2019
  • Sydney: February 13-14, 2019
    plus more….

Connect with our community to gain practical insights and best practices on the future of cloud development, data, IT, and business intelligence. Visit the Microsoft Ignite | The Tour website to find a stop in a city near you.


Back to Top

Updates & Releases


Microsoft Dynamics 365 Online Releases

The Service Updates for Dynamics 365 online version 9.1.0 and 8.2 are now available.

Service Update 9 (9.1.0000.0946 or higher) resolved issues include:

  • Incremental system-wide performance improvements.
  • Selecting "Sales for AI" redirected to another page instead of the "Relationship Insights/Sales for AI" page.
  • When attempting to merge two contacts, the 'First Name' and 'Last Name' fields were not selected by default.
  • Contacts added to the "Attendees" field did not display until the page was refreshed.
  • An error occurred when attempting to open or create account records using the Dynamics 365 Mobile app in offline mode.

Service Update 10 (9.1.0.1064 or higher) resolved issues include:

  • The ribbon was grayed out when an opportunity record was opened and then closed.
  • Contacts could not be synced to Outlook.
  • The Currency field did not populate when an email was converted to a lead.
  • Items on the field search list could not be filtered when more than one filter was applied.
  • The Activity wall loaded slowly. The page froze/crashed if there were too many recipients in the to/cc fields.

Service Update 12 (9.1.0.1201 or higher) resolved issues include:

  • No information displayed in posts generated with a workflow in Unified Interface.
  • Stacked bar charts contained two categories with the same color, instead of four unique colors.
  • Appointments could not be created through the Quick Create form.
  • Opportunities could not be closed in Sales Hub.
  • Reports displayed the wrong info on the Modified By field.

Service Update 1 (8.2.3.0114 or higher) resolved issues include:

  • Phone calls and task items failed to sync from CRM to Exchange.
  • Server-Side Synchronization failed to reopen tasks in Outlook that were reopened in CRM.
  • An error occurred when deleting a managed solution.
  • An error occurred when editing or exporting apps that were added to a solution.

Service Update 2 (8.2.3.0177 or higher) resolved issues include:

  • A read-only field's value was copied twice (i.e. "1234512345 instead of "12345") when copied.
  • The "Post configurations contact" workflow, triggered after creating a new contact on the Account entity, failed periodically.
  • After case merging, 'regarding' of email and custom activities would not update to the master case.
  • The Dynamics 365 add-in in Outlook failed to load pages (accounts, contacts, etc.).
  • An error occurred while attempting to open Account records when Social Insights was present on the form.

Dynamics 365 Resource Scheduling Optimization v3.0 Release

Microsoft is excited to announce the general availability of the Resource Scheduling Optimization (RSO) v3.0 release.

New features include:

  • Maximized preferred resource assignments
  • Best matching skill level
  • Improved logic of handling conflicted bookings
  • User experience improvements to easily re-rank objectives
  • Usability, performance, and quality improvements

For more information on the new features, review this post in the Dynamics 365 Customer Engagement Team Blog.


Field Service and Project Service Automation Updates

The latest update to the Field Service and Project Service Automation solutions for Dynamics 365 is now available. This release includes improvements to quality, performance, and usability, based on customer feedback and requests.

Field Service enhancements (v7.5.5.48)

Resolved issues:

  • Fixed: Script error on work order quick create
  • Fixed: Japanese label localization on work order form
  • Updated SDK libraries to 9.0
  • Fixed: Linked work order sub-grid does not allow searching existing work orders when the user clicks the + command

For information on how to install, update or remove the solution, review this article.

Project Service Automation (v3.2.0.246) Enhancements

Improvements include:

  • Internal performance improvements to upgrade experience.
  • Minor reliability improvements to the project schedule grid.

Resolved issues include:

  • Fixed: Generic SQL Error when creating contract from quote, if customer has custom field maps for multi selection option sets.
  • Fixed: The added or subtracted value results in an un-representable DateTime
  • Fixed: Misalignment of field length between BusinessTransaction msdyn_description and QuoteLine.ProductDescription.
  • Fixed: Missing price information on estimates view when project calendar and user timezone is set to india timezone.

For more information on the Project Service Automation enhancements, review this blog post.


Portal Capabilities for Microsoft Dynamics 365 v9.0.12.12

Portal capabilities version 9.0.12.12 for Microsoft Dynamics 365 is now available. This release includes an updated portal host as well as solution package updates (v9.0.12.10). New solution packages are only applicable for v9.x Dynamics orgs.

The portal host will automatically be updated by Microsoft, but action must be taken by your organization to upgrade the solution packages. Until the solution packages are updated, some enhancements will not be available to portal administrators and/or users.

Resolved issues with Portal Host includes:

  • Editing any component using front side editor on Portal opens a blank page if the component is on a child page which is more than 5 levels down from home page.
  • If an auth provider is configured using both SAML2 and OpenId Connect on portal, then OpenId Connect configuration is broken after SAML2 provider is configured.
  • Subgrid on entity form does not refresh on record delete.

Resolved issues with Portal Solution includes:

  • Source Code Field in Web Template Form doesn't save the content when using Internet Explorer 11.
  • Portal Timeline solution is not updated when Solutions are updated to 8.4.6.2 or 9.0.12.10 version.
  • View Editor on Entity list form doesn't open properly in Internet Explorer 11.

For a full list of all portal updates released to date and their corresponding KB articles, please reference this KB article.


Back to Top

Additional News


Using Clone Solution to remove Managed Solution components

The ability to clone a solution in Dynamics 365 has been around for a while, but did you know you can use the feature to remove managed components, entities or entity assets? For customers already familiar with Solutions and Customizations, you can use this guided lab that showcases a simple example of managed component removal using Clone Solution and explains the “Stage for Upgrade”.

Dynamics 365 App for Outlook Blog Series

With the release of the new version of Dynamics 365 App for Outlook along with v9.0 and the new unified interface, organizations are transitioning from the legacy Dynamics 365 for Outlook client. There have been many questions about the new features, so to help our customers we’re launching a new Dynamics 365 App for Outlook multi-part blog series. The content will be based on a Dynamics 365 Customer Engagement (online) to Exchange Online environment, but much of the information will also be valid for hybrid and on-premise environments.

Part 1 – The Basics:

  • What does the Dynamics 365 App for Outlook offer?
  • App terminology
  • System Requirements

Part 2 – What is supported?:

  • Feature support per client
  • Outlook on the web (OWA)
  • Supported servers

Part 3 – Tracking and Correlation:

  • System Settings
  • Configure email correlation
  • Tracking options

Part 4 – Working with emails:

  • Automatic email tracking
  • FAQs

Part 5 – Working with appointments:

  • Appointment tracking scenarios
  • FAQs

The series is posted to the Dynamics 365 Customer Engagement in the Field blog so check back often for the latest.


Back to Top

Training Corner


Business Applications Bootcamps

The Business Applications Bootcamps are 3-5 day, in-person events around the globe focused on improving functional and technical skills for solution architects, functional consultants, industry experts, application consultants, HR analysts, and data professionals.

The bootcamps focus on 5 workloads:

  • Dynamics 365 for Customer Service
  • Dynamics 365 for Field Service
  • Dynamics 365 for Talent
  • Power platform: PowerApps and Power BI Integration
  • Dynamics 365 for Finance and Operations

Visit BizApps Bootcamps the learn more and to register for a session near you. A Microsoft login account is required.

Free PowerApps "App-in-a-Day" Workshop

As a business leader, you want to react quickly to the changing market and cannot stay dependent on developing a software solution to do that. You want the ability to build a solution to meet your business needs swiftly. With the Microsoft Power Platform, you can build great business apps without writing code.

  • PowerApps: Enable power-users in line of business roles to easily build and deploy custom business apps in both Canvas and Model-driven style of apps.
  • Common Data Service for Apps: Easily bring your data together and quickly create powerful apps using a compliant and scalable data service and app platform integrated right into PowerApps.
  • Microsoft Flow: Enable your line of business specialists and IT pros can build automated workflows intuitively.

Learn how to use these features with a free App-in-a-Day workshop. Classes are happening now, so visit this link to review the agenda and register for a session near you.

Back to Top

Dynamics 365 Customer Engagement – OrgDBOrgSettings configurations might affect instance size/storage

$
0
0

Hi all-

Many of you would be interested in finding out what’s driving storage consumption of you Dynamics 365 Customer Engagement instance. Some would think it’s largely data for entities, i.e. Account, Contact, Lead, Opportunity, Custom etc. Which is true to a large extent but with few exceptions. Organization database also holds system data linked with user records. House keeping such system data is handled by Deletion Service. This post on our CRM PFE Team site explains clean up by Deletion Service. If you are not familiar with Deletion Service, I suggest you read above post to put this altogether.

Now you know the role of Deletion Service, hopefully. Hey, I take that an assumption to continue writing 🙂. I was working with a customer to prepare for an upgrade and noticed some of the system data related tables were significant in size. While it came as surprise for customer their knowledge was claiming system data should be getting cleaned by the system(aka Deletion Service). So, started digging around the Deletion Service behavior for the organization in question. Deletion service executions were successful, no errors! Further going into the details of few large tables, it came to light that system data was retaining longer than usual. Found several OrgDBOrgSettings were set differently for this Org.

We could have restored to default values but chose to discuss retention requirements, general guidance and adjusted the settings accordingly. Once we adjusted these settings, next run of Deletion Service took care of reducing size of respective tables.

From above learning, here are the OrgDBOrgSettings those control Deletion Service retention along with description:

Setting Name

Description

ExpireChangeTrackingInDays        

Maximum number of days to keep change tracking deleted record ID's. You want this value larger than the max# of days any change tracking dependent services sync with your system. Default is 30 days.

ExpireSubscriptionsInDays

Max number of days before deleting inactive Outlook client subscriptions. We recommend you keep this to the default unless you absolutely need to change it, be mindful of keeping the tracking info too long, or deleting it too soon.

ExportedExcelRetentionWindow

The number of days to temporarily store Excel exported Office Document Records. 30 days max was selected arbitrarily as this is only a cache. Must be at least 2.

MailboxStatisticsPersistenceTimeInDays

If value is 0, don't store ANY Mailbox Statistics data, if the value is greater than zero then store that number of days statistics data. Max value arbitrarily chosen is 1 year, this generates at lot of data so 1 year should be plenty of time.

OfficeDocumentPersistenceTimeInDays

The number of days to temporarily store Office Document Records. 30 days max was selected arbitrarily as this is only a cache.

 

These settings can be retrieved updated using OrgDBOrgSettings command line tool described in this KB article or OrgDBOrgSettings Solution.

Hope this helps!

Bhavesh Shastri

Dynamics 365 Monthly Update-January 2019

$
0
0
Quick Links: Featured News | Updates and Releases | Additional News | Training Corner

Featured News


Dynamics 365 Spring ’19 Release

Dynamics 365 (online) delivers new capabilities and functionalities through two major updates a year in April and October. Release notes will be published months prior to each major release update to help customers and partners plan for the new capabilities.

The next major update will take place in April 2019. Below are the details from the upcoming Dynamics 365 Release Calendar for Spring ‘19:

Activity Date
Release Notes available January 21, 2019
Preview available February 1, 2019
Release Notes updates February 21, 2019
General availability April 5, 2019

Starting February 1, 2019, customers can preview the new features by opting-in to enable them in the Power platform Admin Center of their production, trial and sandbox Dynamics 365 instances. For detailed instructions on opting-in, verifying your release version and how to prepare for the Spring ’19 Release, review Previewing April 2019 release functionalities and updates for Dynamics 365 for Customer Engagement.

Stay informed on the major updates for Dynamics 365 by reviewing the Business Applications Release Notes, the Release Schedules and the Dynamics 365 Product Road Maps.

PowerApps Solution Checker

The challenge of increasing the performance of PowerApps customizations and the pressure of ensuring a quality release when faced with new project timelines can be daunting when you’re not sure where to start. To help with this, the PowerApps team has rolled out a new Solution Checker, available now in public preview.

With Solution checker, customers can inspect their code directly in PowerApps against a set of best practice development rules specific to customizing and extending the Common Data Service (CDS) for Apps platform. The outputs are rich detailed reports listing issues, severity, location, with some links to detailed prescriptive guidance on how to fix the problem.

For more details on the Solution Checker and how to enable it, review Make higher quality Apps with Solution checker on the PowerApps Blog.

Dynamics 365 Channel Integration Framework – Bring your own channel provider

Microsoft is excited to announce the general availability of the Dynamics 365 Channel Integration Framework. Channel Integration Framework is a set of APIs (methods, events, and protocols) that enable developers and partners to build immersive communication experiences such that third party communication widgets running on the channel provider cloud can interact with Dynamics 365.

Before the Channel Integration Framework (CIF), developers were required to create unsupported customizations and manipulations to embed their channel widgets in Dynamics 365. With CIF, customer enjoy some of the following benefits:

  • CIF is channel, web browser and operating system agnostic. Customers can build any channel with JavaScript based widgets and integrate any cloud-based channel of their choice.
  • Seamlessly integrate several providers by using the Channel Integration Framework administration configuration app.
  • The framework is extensible for the configuration of two-communication between the channel and Dynamics 365 Unified Interface Apps.

For more information on the Channel Integration Framework, review this post on the Dynamics 365 Customer Engagement Team Blog.

Back to Top

Updates & Releases


Dynamics 365 for Blackberry is deprecated

As of December 3, 2018, Microsoft Dynamics 365 for Blackberry App is deprecated and will be removed from the iOS App Store on October 31, 2019. Microsoft will continue to provide security and other critical updates to the Dynamics 365 for Blackberry App until October 31, 2019, but will not release any additional features or functionalities within the app. After October 31, 2019, the Dynamics 365 for Blackberry App will be removed from the App Store, and support will end.

For more information, review Important changes (deprecations) coming in Dynamics 365 Customer Engagement.

Knowledgebase search powered by Dynamics 365 Relevance Search

The Knowledge base (KB) search control in Dynamics 365 is now powered by Relevance search. This change allows administrators to fine-tune the KB search to meet their business requirements and empowers agents to find the most relevant KB articles quickly.

Additional features include:

  • Highlighted search term matches
  • Search tuning on any knowledge article field
  • Search in notes and attachments of Knowledge Articles

For more details review Improve Knowledge Article search results with Dynamics 365 Relevance Search.

Microsoft Dynamics 365 Online Release

The Service Updates for Dynamics 365 online version 9.1.0 are now available.

Service Update 14 (9.1.0.1401 or higher) resolved issues include:

  • Tab names intermittently displayed incorrectly as "Tab" instead of displaying the appropriate label.
  • When synchronizing contacts from Outlook to Dynamics using the Outlook app, the street portion of the contact's address moved to Address 3. After synchronizing again, the street was deleted from the contact's address.
  • Custom filters on the Lookup field did not function in Unified Client Interface.
  • The Insert Hyperlink button in the email body of a workflow's Send Email function did not work and gave a null value.

Service Update 16 (9.1.0.1604 or higher) resolved issues include:

  • Duplicate appointments were created in Dynamics and Exchange when the "Track Appointments From NonOrganizer" setting was used.
  • Documents uploaded to SharePoint online from Dynamics online were not visible in the sub-grid.
  • An error occurred when attempting to reactivate and qualify a lead.
  • Incorrect values appeared when hovering over the fields of a custom entity.

Microsoft Dynamics 365 (on-premises) Update 2.3

Microsoft Dynamics 365 (on-premises) Update 2.3 is now available.

Resolved issues include:

  • The Remaining Terms values failed to update when Entitlements were saved.
  • Users could not rename the "Case" button label.
  • SLAs created on non-working days (such as weekends and holidays) started immediately rather than obeying the non-working time.
  • The ribbon menu was displaying even when appointment were set to "Read-only".

Overview and Release Details: https://blogs.msdn.microsoft.com/crminthefield/2018/12/12/podcast-and-overview-microsoft-dynamics-365-on-premises-update-2-3/

Knowledge Base Article: https://support.microsoft.com/en-us/help/4467675

Download link: https://www.microsoft.com/en-us/download/details.aspx?id=57523

Field Service Updates

The latest update to the Field Service solutions for Dynamics 365 is now available. This release is compatible with Dynamics 365 9.x.

Field Service enhancements (v8.3.0.255)

Improvements:

  • The Field Service module sitemap now includes Connected Field Service entities.

Resolved issues:

  • Fixed: Upgrade Bug – Booking is updated with GroupId before the record is created.

Feature updates include:

  • The Connected Field Service solution is now available out of the box with Field Service, eliminating the need to install the additional solution package.
  • There is a new Field Service Mobile application
  • Push notifications can be sent to the Field Service Mobile application using the Field Service Mobile Entity Push Notification workflow action.

For more information, review Release Notes for Field Service Version 8, Update Release 3.

Back to Top

Project Service Automation Updates

The latest updates to the Project Service Automation solutions for Dynamics 365 are now available. These releases are compatible with Dynamics 365 9.x.

Project Service Automation (v2.4.8.47) Enhancements

Improvements include:

  • Users can delete products lines from a Project Invoice when the invoice is in draft state.

Resolved issues include:

  • Project Approval had overlapping command sequences for "Approve" and "Reject" impacting the Ribbon Work Bench.
  • WBS failed to open for empty projects when the project start date and end date was the same.
  • Javascript error impacting contract line and quote line filtering when Maplytics was installed.

Project Service Automation (v2.4.8.52) Enhancements

Resolved issues include:

  • Requirement Name in the schedule assistant demand panel showed the incorrect name when the name contained apostrophes
  • Issue when users tried to create a booking alert when they were assigned to a child business unit
  • Issue when launching the schedule assistant with certain time zone combinations, related to daylight savings time.

To update to these releases, visit the Admin Center for Dynamics 365 solutions page to install. For details, refer How to Install, Update a Preferred Solution.

Voice of the Customer Updates

The latest updates to the Voice of the Customer solutions for Dynamics 365 are now available:

Voice of the Customer version 9.0.1371.8 is compatible with Dynamics 365 version 9.0 and above.

Voice of the Customer version 9.0.1371.7 is compatible with Dynamics 365 version 8.2.

New and updated features:

  • Customers can now delete a file that is uploaded in response to the question type File upload by clicking the Delete File button in the command bar.

Resolved issues:

  • When a respondent selected a smiley face in a rating question, all the preceding smileys were selected.
  • The survey scoring values reverted to their default values when saving the question.
  • When a respondent clicked on the text of a radio button, the radio button was not selected.
  • Survey did not open in the language specified in the survey email.
  • Respondent and case information was not associated with the responses if the corresponding invite was in the closed state.

To update to these releases, visit the Admin Center for Dynamics 365 solutions page to install. For details, refer How to Install, Update a Preferred Solution.

Dynamics 365 for Marketing Update

The latest update for Dynamics 365 for Marketing is now available. This update includes several new features, performance and stability improvements.

New and updated features:

  • Event Website: The fully functioning sample event website included with Dynamics 365 for Marketing can now be downloaded as an angular JavaScript project that can be customized and published anywhere.
  • CAPTCHA: The CAPTCHA can now be removed from the event registration form with a simple configuration setting update.
  • Member Count: An accurate member count for live segments is now available to replace the estimated member count.

For more details on all the changes for Dynamics 365 for Marketing and how to get the update, review this announcement on the Dynamics 365 Customer Engagement Team Blog.

Back to Top

Additional News


Dynamics 365 for Marketing Sender Reputation

One of the fastest ways to lose sender reputation deliverability rates with email marketing is to generate a high number of hard bounces and spam complaints from your email blasts. Internet watchdog organizations keep an eye out for red flags in email content and sending behavior. They assign a sender reputation to each IP address that sends email. The lower the reputation the more difficult it is to land in an Inbox. Some of the key ways to maintain a good sender reputation is to:

  • Include an unsubscribe link
  • Include your organization's physical address
  • Include text-only content that matches HTML content
  • Don't send image-only messages

Dynamics 365 for Marketing includes features that help customers meet these requirements. It can also check each message before it is published to make sure it conforms with the requirements. If any hard bounces are detected, Dynamics 365 for Marketing will stop sending to those addresses in the future.

For more information on how Dynamics 365 for Marketing can help implement good data quality for your marketing campaigns, review this post in the Dynamics 365 Customer Engagement Team Blog.

Dynamics 365 App for Outlook Blog Series

With the release of the new version of Dynamics 365 App for Outlook along with v9.0 and the new unified interface, organizations are transitioning from the legacy Dynamics 365 for Outlook client. There have been many questions about the new features, so to help our customers we’ve created a Dynamics 365 App for Outlook multi-part blog series.

The content will be based on a Dynamics 365 Customer Engagement (online) to Exchange Online environment, but much of the information will also be valid for hybrid and on-premise environments.

Part 6 – Working with Contacts:

  • Where do I find Contacts in the App for Outlook?
  • Modify the Contacts View
  • Create, Track and Link Contacts
  • Search Contacts

Part 7 – Helpful Tips:

  • Set Regarding and Track records
  • Access Views
  • Modify the App for Outlook Sitemap

Part 8 – Email Governance:

  • Options to restrict or filter email information

The series is posted to the Dynamics 365 Customer Engagement in the Field blog.

Dynamics 365 Reports: SRS Data Connector Error

Have you ever received this error after attempting to run a report in Dynamics 365?

clip_image004

Maybe you’ve tried removing and reinstalling the Connector, but the error remains. Before submitting a support case, check out this article from one of our Dynamics 365 Premier Field Engineers with guidance on how to troubleshoot and resolve the issue: Dynamics CRM Reports complaining Reporting extension(SRS Data Connector) is not installed.

Back to Top

Training Corner


Better Together: Office 365 + Dynamics 365 + LinkedIn

As part of an ongoing effort to accelerate sales with OneMicrosoft, a video demonstration of Microsoft’s relationship analytics is now available. The Better Together video showcases how Office 365, Dynamics 365 and LinkedIn Sales Navigator are better together and empower customers.

The video showcases how Microsoft business applications give sales teams an advantage to close sales using:

  • Office 365
  • Dynamics 365 App for Outlook
  • Dynamics 365
  • Power BI
  • Relationship Analytics
  • Relationship Health
  • LinkedIn Sales Navigator

Dynamics 365 AI for Sales Demo

The Microsoft Dynamics 365 AI for Sales service includes a user on-boarding video that highlights how Microsoft is democratizing data science and infusing machine learning to improve sales outcomes. Learn more about the features of the Dynamics 365 AI for Sales service and check out the on-boarding video here in the Dynamics 365 Community site.

Back to Top
Viewing all 103 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>