Archive

Author Archive

Deploy Microsoft Dynamics 365 for Outlook by using Group Policy

July 11th, 2018 DynamicsMSCRM Comments off

Deploy Microsoft Dynamics 365 for Outlook by using Group Policy

Group Policy provides an infrastructure for centralized configuration management of the operating system and applications, such as Dynamics 365 for Outlook, that run on the operating system. The Group Policy settings you create are contained in a Group Policy Object (GPO). To create and edit a GPO, use the Group Policy Management Console (GPMC). By using the GPMC to link a GPO to selected Active Directory sites, domains, and organizational units (OUs), you apply the policy settings in the GPO to the users and computers in those Active Directory objects. More information: Group Policy Overview

Using Group Policy, you can deploy Dynamics 365 for Outlook. This topic shows you how to perform a Group Policy-based software deployment that publishes Dynamics 365 for Outlook making it available for users to install from Control Panel. When you publish software for users, you give them the opportunity to decide if and when they want to install it.

Important

You must run the Microsoft Dynamics CRM for Outlook Setup program (SetupClient.exe) by using the administrative installation option (/A) to create a Windows Installer package (CRMClient_bitversion.msi) for Group Policy deployment. You cannot use the Windows Installer package (Client.msi) that is included with the Dynamics 365 for Outlook installation files to deploy by using Group Policy. For more information about how to perform an administrative installation, see Install Microsoft Dynamics 365 for Outlook.

To complete this procedure, you must be a member of the Domain Administrators security group, the Enterprise Administrators security group, or the Group Policy Creator Owners security group.

Preparing Dynamics 365 for Outlook for a Group Policy deployment

Use this procedure to create the CRMClient_bitversion.msi file that is required for a Dynamics 365 for Outlook Group Policy deployment.

Create the CRMClient_bitversion.msi file

  1. Before you build the CRMClient_bitversion.msi file, you can edit the Default-Client_Config.xml file that is included with the installation files. This file is used by the Microsoft Dynamics 365 for Outlook Configuration Wizard to establish settings, such as the organization URL, after Dynamics 365 for Outlook is installed on the user’s computer. Although this step is optional, it can simplify Dynamics 365 for Outlook configuration for Dynamics 365 users. More information: Step 2: Configure Microsoft Dynamics 365 for Outlook by using an XML configuration file
  2. Determine the distribution share, and then run Microsoft Dynamics CRM for Outlook Setup to build the administrative installation files.

    Important

    The CRMClient_bitversion.msi file is used as the package for Group Policy software installation. After you follow this procedure, users can select Dynamics 365 for Outlook in Control Panel for on-demand installation. You can’t use the CRMClient_bitversion.msi file directly to install Dynamics 365 for Outlook.

    1. Create a network share that all Dynamics 365 for Outlook users will have access to. This share will be the distribution location for the GPO.
    2. Run SetupClient.exe at the command prompt by using the /A and /targetdir parameters. The /A parameter specifies an administrative installation, and /targetdir parameter specifies the distribution share that you created in the previous step. For more information about Microsoft Dynamics CRM for Outlook Setup command prompt parameters, see Step 1: Install files.Example:
      setupclient.exe /a /q /targetdir \\FileShare\CRMforOutlook
      
    3. Consider using Microsoft Distributed File System (DFS) to help improve the security and availability of your distribution points. For more information about DFS, see DFS Namespaces and DFS Replication Overview. We recommend that you understand the DFS features before you configure your distribution point servers.
  3. Create the Group Policy Object (GPO) and target the application to Dynamics 365 users. To do this, follow these steps:
    1. On a domain controller in the domain where Dynamics 365 is installed, start Group Policy Management.
    2. In Group Policy Management, expand Forest, Domains right-click the domain, and then click Create a GPO in this domain, and Link it here.
    3. In the New GPO dialog, type a name for the GPO, such as Microsoft Dynamics 365 Users, and then click OK.Creating a GPO at the domain level configures the GPO with domain-wide scope.
    4. In the group policy pane, right-click the GPO that you created in the previous step, and then click Edit.The Group Policy Management Editor opens.
    5. In Group Policy Management Editor, under User Configuration, expand Policies, and then expand Software Settings.
    6. Right-click Software Installation, point to New, and then click Package.
    7. Type the full path or locate the Dynamics 365 for Outlook Windows Installer package (CRMClient_64.msi or CRMClient_32.msi) that was created by the administrative installation, and then click Open. For more information about how to create an administrative install package for Dynamics 365 for Outlook, see the /A parameter in Install Microsoft Dynamics 365 for Outlook using a Command Prompt.

      Important

      The Dynamics 365 for Outlook administrative installation folders must be on a network share that can be read-accessed by Dynamics 365 users in the domain.

      Tip

      By default, the package name is Microsoft Dynamics 365 <version> for Outlook for both 32-bit and 64-bit packages. Consider renaming the package to Dynamics 365 for Outlook <version> 64-(bit) or Dynamics 365 for Outlook <version> (32-bit). This name appears in Control Panel in the list of programs to install from the network.

    8. In the Deploy Software dialog, select Publish to publish the Dynamics 365 for Outlook application, and then click OK.
    9. By default, Dynamics 365 for Outlook is available in Control Panel for all authenticated users the next time that they log on to the domain. To limit the scope to a specific organizational unit (OU), group, or individual user, in Group Policy Management, expand Group Policy Objects, and click the GPO named Microsoft Dynamics 365 Users, and then add or remove the security objects that you want, such as a group, in the Security Filtering area of the publication on the Scope tab.

Publish versus Assign

When you publish an application by using GPO deployment, it is made available for users to install by using Program and Features (or in previous versions of Windows, Add or Remove Programs) in Control Panel. Assigned applications are installed when a user logs on to the domain.

Note

Dynamics 365 for Outlook doesn’t support application assignment through GPO installation. For more information about publishing versus assigning software, see the Group Policy deployment documentation for your operating system.

  • Share/Bookmark
Categories: D365, Outlook Tags:

Microsoft Flow Free, User show up on Dynamics CRM

July 9th, 2018 DynamicsMSCRM Comments off

If Microsoft Flow Free is assigned to an O365 user, this user will show up in D365 (CRM).

The reason the users synced into CRM relates to new features that we are implementing which integrates some of our applications with CRM. An example of this can be read here: https://blogs.msdn.microsoft.com/crm/2018/03/21/whats-new-in-the-dynamics-365-admin-center/ In order to disable the users from being synced into CRM you will need to disable the PowerApps/Flow/Common Data Services Viral Licenses in O365.

  • Share/Bookmark
Categories: D365 Tags:

Dynamics 365 for Outlook is unable to render webpages

June 20th, 2018 DynamicsMSCRM No comments

When attempting to render webpages via the Outlook folder pane using the Microsoft Dynamics 365 for Microsoft Outlook add-in (Outlook client), the view pane remains blank and “Waiting for a page to be retrieved from a CRM server…” displays. The pane never loads the corresponding webpage.

Cause


The Dynamics 365 for Outlook add-in relies on customized roaming home pages in order to render webpages within Outlook. The October 2017 Microsoft Outlook security update disables roaming home pages in Outlook to address a significant vulnerability with the application, and as such, inadvertently causes the add-in to fail.

More information on why this issue is occuring can be found at the following article from Outlook:

Outlook Home Page feature is missing in folder properties

Versioning Information


All versions of the Microsoft Dynamics 365 for Microsoft Outlook add-in family are affected by this issue. This includes Microsoft Dynamics CRM 2016 for Microsoft Office Outlook, Microsoft Dynamics CRM 2015 for Microsoft Office Outlook, and Microsoft Dynamics CRM 2013 for Microsoft Office Outlook.

This also affects all versions of the Dynamics 365/ CRM organization that the add-in is connecting to.

The Outlook Security update versioning information is found below:

Security Update for Microsoft Outlook 2010 (KB4011089) 32-Bit Edition
Security Update for Microsoft Outlook 2010 (KB4011089) 64-Bit Edition
Security Update for Microsoft Outlook 2010 (KB4011196) 32-Bit Edition
Security Update for Microsoft Outlook 2010 (KB4011196) 64-Bit Edition
Security Update for Microsoft Outlook 2013 (KB4011178) 32-Bit Edition
Security Update for Microsoft Outlook 2013 (KB4011178) 64-Bit Edition
Security Update for Microsoft Outlook 2016 (KB4011162) 32-Bit Edition
Security Update for Microsoft Outlook 2016 (KB4011162) 64-Bit Edition

Any future cumulative Outlook updates will contain these Security Updates and will cause this issue to occur, such as the following updates:

Update for Microsoft Outlook 2013 (KB4011252) 32-Bit Edition
Update for Microsoft Outlook 2013 (KB4011252) 64-Bit Edition
Update for Microsoft Outlook 2016 (KB4011240) 32-Bit Edition
Update for Microsoft Outlook 2016 (KB4011240) 64-Bit Edition

Resolution


Due to this security update resolving multiple significant vulnerabilities within the Microsoft Outlook application, it must remain installed. In order to re-enable roaming home pages as a workaround while a permanent resolution is developed, a registry key must be added to the local client machines running the Microsoft Dynamics 365 for Outlook application. This key must be installed either through direct registry edit or via Group Policy in your organization.

Important

The DWORD value for this key is being set to 2 in order for it to be defined in a future security update.

The following registry key is dependent on the version of Microsoft Outlook installed:

Microsoft Outlook 2016:

[HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\Security] “EnableRoamingFolderHomepages”=dword:00000002

Microsoft Outlook 2013:

[HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Outlook\Security] “EnableRoamingFolderHomepages”=dword:00000002

Microsoft Outlook 2010:

[HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Outlook\Security] “EnableRoamingFolderHomepages”=dword:00000002

Once this registry key is added to the local client, Microsoft Outlook must be restarted and the add-in will be able to render webpages without issue.

  • Share/Bookmark
Categories: Uncategorized Tags:

You do not have the ‘ISV Extensions’ privilege assigned to your security role.

March 23rd, 2018 DynamicsMSCRM No comments

Here are the steps to correct this issue.

1 Open the Main Custom form. Go to Settings > Customization > Customize the System > Entities > Account > Form > Select the Entity Main form.

The following screen appears:

2 Add the Insights 4.0 connector
  • Select the Section and click the Insert tab.
  • On the Insert tab, click the Web Resource icon.

3 Add the Web Resource properties On the Web Resources page, enter the following properties:

  • Search and select the iv_/webpages/summary_mashup.htm web resource.
  • Enter the Field Name and Label Properties field values as WebResource_Insights and Insights.
  • Enter the Web Resource Custom Parameter(data) property values as “solutionVersion=4.1&crm_version=v123” (THIS IS AN OLD VERSION, IF YOU HAVE FILLED THIS FIELD, KEEP IT, DO NOT EDIT IT).
  • Select the Pass record object-type code and unique identifier as parameters and Enable for Tablet check boxes.

4 Add the Formatting tab properties Select the Formatting tab and change the following values:

  • Select the One-Column check box.
  • Enter the value Number of Rows as 20.
  • Select the Automatically expand to use available space check box.
  • Deselect the Display Border check box.
  • Click OK.

5 Create the Insights Navigation Link page Double-click on the Common tile to make it editable. On the Custom Form page, select Insights in the left pane and click the Navigation Link icon as illustrated below:

Note: If the Insights link does not exist under the Common tile, create a new Navigation Link.

6 Add Navigation Link properties On the Navigation Link dialog box, enter the following information:

  • Name as Insights.
  • Icon as iv_/images/insights_32px.png
  • Search and select the Web Resource URL as iv_/webpages/detail_mashup.htm.
  • Click OK.

7 Go to the Form Properties page Select the Insights tab and click the Form Properties icon to bring up the Form Properties page.

8 Modify the custom form properties On the Form Properties page, select the Parameters tab and enter the following information:

  • Click the + Add icon.
  • Enter the Name as iv_onLoadAction.
  • Enter the Type as SafeString.
  • Click OK.

9 Save and Publish Click Save, then click Publish.

Note: Repeat steps 1-9 for Account, Contact, Opportunity, and Lead Microsoft Dynamic CRM entities.

  • Share/Bookmark
Categories: Uncategorized Tags:

Transport Layer Security (TLS) 1.2 Connectivity Requirements for Dynamics 365 (Online), version 9.0

February 7th, 2018 DynamicsMSCRM No comments

Summary
Starting with Dynamics 365 (online) version 9.0, Microsoft will begin requiring connections to customer engagement applications to utilize TLS 1.2 (or better) security. Any connections to Dynamics 365 (online), version 9.x will fail if they do not use TLS 1.2 security protocol. This will impact several Dynamics services including access to the Dynamics 365 Customer Engagement (CRM) web application.

More Information

TLS 1.0 deprecation plan may require the following:

  • Code analysis to find/fix hardcoded instances of TLS 1.0 (or instances of older TLS/SSL versions).
  • Network endpoint scanning and traffic analysis to identify operating systems using TLS 1.0 or older protocols.
  • Full regression testing through your entire application stack with TLS 1.0 disabled.
  • Migration of legacy operating systems and development libraries/frameworks to versions capable of negotiating TLS 1.2.
  • Compatibility testing across operating systems used by your business to identify any TLS 1.2 support issues.
  • Coordination with your own business partners and customers to notify them of your move to deprecate TLS 1.0.
  • Understanding which clients may not interoperate by disabling TLS 1.0

How will you or your customers be impacted?

Any connections to Dynamics 365 (online), version 9.x will fail if they do not use TLS 1.2 security protocol. This will impact several Dynamics services (listed below), including access to the Dynamics 365 Customer Engagement web application.

A quick way to determine what TLS version will be requested by various clients when connecting to your online services is by referring to the Handshake Simulation at Qualys SSL Labs.

Supported versions of Internet Explorer and Microsoft Edge

Supported non-Internet Explorer web browsers

  • Mozilla Firefox (latest publicly-released version) running on Windows 10, Windows 8.1, Windows 8, or Windows 7
  • Google Chrome
  • Google Chrome (latest publicly-released version) running on Windows 10, Windows 8.1, Windows 8, Windows 7, and Android 10 tablet
  • Google Chrome (latest publicly-released version) running on Mac OS X 10.8 (Mountain Lion), 10.9 (Mavericks), or 10.10 (Yosemite)
  • Apple Safari (latest publicly-released version) running on Mac OS X 10.8 (Mountain Lion), 10.9 (Mavericks), 10.10 (Yosemite), or Apple iPad

Supported versions of Microsoft Office

  • Microsoft Office 365
  • Microsoft Office 2016
  • Microsoft Office 2013
  • Microsoft Office 2010

Ensuring support for TLS 1.2 across deployed operating systems
Many operating systems have outdated TLS version defaults or support ceilings that need to be accounted for.  Usage of Windows 8/Server 2012 or later means that TLS 1.2 will be the default security protocol version:

Error Examples
Below are some potential connectivity errors you might encounter when non-TLS 1.2 security protocol is used:

Browser error:

  • Can’t connect securely to this page
  • This might be because the site uses outdated or unsafe TLS security settings. If this keeps happening, try contacting the website’s owner.

Connector error:

Microsoft.Xrm.Tooling.CrmConnectControl Information: 8 : Login Status in Connect is =  Validating connection to Microsoft Dynamics CRM…
Microsoft.Xrm.Tooling.Connector.CrmServiceClient Error: 2 : ERROR REQUESTING Token FROM THE Authentication context
Microsoft.Xrm.Tooling.Connector.CrmServiceClient Error: 2 : Source  : mscorlib
Method   : ThrowIfExceptional
Error        : One or more errors occurred.
Stack Trace              : at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions)
at System.Threading.Tasks.Task`1.GetResultCore(Boolean waitCompletionNotification)
at System.Threading.Tasks.Task`1.get_Result()
at Microsoft.Xrm.Tooling.Connector.CrmWebSvc.ExecuteAuthenticateServiceProcess(Uri serviceUrl, ClientCredentials clientCredentials, UserIdentifier user, String clientId, Uri redirectUri, PromptBehavior promptBehavior, String tokenCachePath, Boolean isOnPrem, String authority, Uri& targetServiceUrl, AuthenticationContext& authContext, String& resource)

Inner Exception Level 1:

Source: Microsoft.IdentityModel.Clients.ActiveDirectory
Method: Close
Error: Object reference not set to an instance of an object.

Stack Trace: at Microsoft.IdentityModel.Clients.ActiveDirectory.HttpWebResponseWrapper.Close()
at Microsoft.IdentityModel.Clients.ActiveDirectory.AuthenticationParameters.d__0.MoveNext()
— End of stack trace from previous location where exception was thrown —
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.IdentityModel.Clients.ActiveDirectory.AuthenticationParameters.d__8.MoveNext() ”

Developer tools error:

Inner Exception Level 1 :

Error : The underlying connection was closed: An unexpected error occurred on a send.
Stack Trace: at System.Net.HttpWebRequest.GetResponse()

at System.ServiceModel.Description.MetadataExchangeClient.MetadataLocationRetriever.DownloadMetadata(TimeoutHelper timeoutHelper)
at System.ServiceModel.Description.MetadataExchangeClient.MetadataRetriever.Retrieve(TimeoutHelper timeoutHelper)

Inner Exception Level 2 :

Error : Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.
Stack Trace: at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)

at System.Net.FixedSizeReader.ReadPacket(Byte[] buffer, Int32 offset, Int32 count)
at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest) ”

How to be Proactive
Microsoft recommends customers proactively address weak TLS usage by removing TLS 1.0/1.1 dependencies in their environments and disabling TLS 1.0/1.1 at the operating system level where possible. Given the length of time TLS 1.0/1.1 has been supported by the software industry, it is highly recommended that any TLS 1.0/1.1 deprecation plan include the following:

  • Application code analysis to find/fix hardcoded instances of TLS 1.0/1.1.
  • Network endpoint scanning and traffic analysis to identify operating systems using TLS 1.0/1.1 or older protocols.
  • Full regression testing through your entire application stack with TLS 1.0/1.1 and all older security protocols disabled.
  • Migration of legacy operating systems and development libraries/frameworks to versions capable of negotiating TLS 1.2.
  • Compatibility testing across operating systems used by your business to identify any TLS 1.2 support issues.

How you or your customers can avoid being impacted.

  • Custom Windows clients built utilizing .NET 4.5.2 (web and native client applications)
    • Custom Windows clients built utilizing .NET 4.5.2 can be fixed by recompiling on .NET 4.6.2. Versions of .NET 4.6.2 and higher implement a process that will seek the highest possible security transport that the host operating system supports.
    • If you are unable to do this, you can utilize a registry setting on Windows that will force .NET to utilize the highest possible security standard. Please Note: This is a machine-wide setting and may have undesired affects. It is recommended that you or your customer utilize the method of recompiling to .NET 4.6.2 or higher. The registry settings that will force .NET 4.5.2 to prefer TLS 1.2 machine-wide are documented in the article Microsoft Security Advisory 2960358 in the section “Suggested Actions” under “Manually disable RC4 in TLS on systems running .NET Framework 4.5/4.5.1/4.5.2″
  • Non .NET Clients (web and client applications)
    • Please check with the framework or language provider to determine how to configure your application to utilize TLS 1.2
  • Dynamics 365 for Microsoft Outlook
    • Download and install Version 8.2.2.137. This is required to connect Dynamics 365 for Outlook with Dynamics 365 (online), version 9.0.
  • Developer Tools
    • Download latest version of tools, used in development, from NuGet. This is required to connect to Dynamics 365 (online), version 9.0.
  • Unified Service Desk

To learn more about removing dependencies on TLS 1.0/1.1 and updating to TLS 1.2 please review the following whitepaper: “Solving the TLS 1.0 Problem

  • Share/Bookmark
Categories: Security, TLS 1.2 Tags:

Test Your Browser’s SSL Implementation

February 7th, 2018 DynamicsMSCRM No comments
Categories: Uncategorized Tags:

Changes coming Dynamics 365 Customer Engagement (CRM V9)

February 7th, 2018 DynamicsMSCRM No comments

This apply’s to Dynamics 365 Customer Engagement as of version 9

More Information

Service scheduling in Dynamics 365 for Customer Service is deprecated
The Unified Resource Scheduling solution is included with Dynamics 365 for Field Service. With this solution, you can automatically set up the system to schedule multiple booking requirements on a recurring basis. This minimizes overall travel time and maximizes efficient use of all resources. It takes many constraints into account, such as resource availability, skills required, working hours, duration, and time windows to optimize the schedule.

The existing service scheduling functionality using the Service activity is deprecated and will be removed in a future major release. Service scheduling features will be included in the Unified Resource Scheduling solution. This solution integrates seamlessly with Dynamics 365, and will work with Dynamics 365 for Customer Service. The Unified Resource Scheduling solution will provide feature parity with the existing service scheduling feature.

Existing service scheduling users will be provided advance notice for a timebound migration to the new service-scheduling capabilities.

More information: Help & Training: Use Resource Scheduling Optimization to schedule multiple booking requirements on a recurring basis

Dialogs are deprecated
You can use a Dialog process to create an interactive step-by-step data entry form that requires user input to start and run to completion. When you start the dialog process, a wizard-like interface is presented; users make selections or enter data as they progress through each page of the wizard.

Dialogs are deprecated and are replaced by mobile task flows (available as of the December 2016 update), and business process flows. Both task flows and business process flows will continue to evolve to make the transition easier.

Usage of Parature knowledgebase as the Dynamics 365 knowledge management solution is deprecated
Usage of Parature from Microsoft knowledgebase as the Dynamics 365 knowledge management solution is deprecated. This feature is replaced by Knowledge Management features in Dynamics 365.

The Knowledge Solution setting in the Knowledge Base Management Settings dialog box, which provides a connection between Dynamics 365 and Parature from Microsoft, will be removed in a future major release of Dynamics 365.

Project Service Finder app is deprecated
The Project Service Finder App, available for use with Dynamics 365 for Project Service Automation, is deprecated. The legacy application will be supported for associated legacy Project Service Automation releases in accordance with Microsoft’s Modern Lifecycle Policy. The functionality available through this app will be available in a future release of Dynamics 365 in the Dynamics 365 for Project Service Automation application.

Contracts, Contract Line Items, and Contract Templates entities are deprecated
The Contracts, Contract Line Items, and Contract Templates entities are deprecated and will be removed in a future major release of Dynamics 365. This functionality has been replaced by entitlements in Dynamics 365 for Customer Service.

Standard SLAs in Dynamics 365 for Customer Service are deprecated
Standard service level agreements (SLA Type field is set to Standard) are deprecated and will be removed in a future major release of Dynamics 365. Standard SLAs are replaced by enhanced SLAs. More information: TechNet: Enhanced service level agreements

Relationship Roles are deprecated
Relationship Roles (Settings>Business Management>Relationship Roles) are deprecated and will be removed in a future major release of Dynamics 365. This feature is replaced by Connection Roles. More information: Help and Training: Create connections to view relationships between records.

Mail Merge is deprecated
In Dynamics CRM 2016 (version 8.0), we introduced server-side document generation using Word and Excel templates. You can use these templates to provide standardized documents or customized data analysis for your organization.

Mail merge from previous versions is deprecated. This includes the mail-merge Word add-in as well as mail-merge templates (Settings>Templates>Mail Merge Templates).

More information: Help & Training: Create Word and Excel templates from Dynamics 365 data

Announcements are deprecated
Announcements (Settings>Administration>Announcements) are deprecated and will be removed in a future major release of Dynamics 365.

Ready-to-use business processes available through Add Ready to Use Business Processes setting are deprecated
Ready-to-use business processes available through the Add Ready-to-Use Business Processes setting (Settings>Data Management>Add Ready-to-Use Business Processes) are deprecated and will be removed in a future major release of Dynamics 365. You can find ready-to-use business processes on Microsoft AppSource.

Some client APIs are deprecated
The following client APIs are deprecated in the current release to reorganize the Xrm client API object model to better align with the need of using the same client scripts without having to change them based on the context or the client (web client or the new Unified Interface) where they run. You should plan to use the new client APIs mentioned in the Replacement Client API column instead of the deprecated ones. The deprecated client APIs will continue to be available and supported until they are officially removed from a future major release of Dynamics 365.

For information about the new client APIs, see Client scripting in Customer Engagement using JavaScript

EntityMetadata.IsInteractionCentricEnabled property is deprecated
All entities supported in the Unified Interface are now enabled for the interactive experience in the new Customer Service Hub app. This implies that the EntityMetadata.IsInteractionCentricEnabled property, which indicates whether an entity can be enabled for interactive experience, is no longer relevant. The corresponding setting for this property in the Customization tool, Enable for interactive experience, is removed in the current release, and the EntityMetadata.IsInteractionCentricEnabled property will be removed from the future version of Dynamics 365 SDK for Customer Engagement.

Silverlight (XAP) web resource is deprecated
The Silverlight (XAP) web resource is deprecated on the web client, and is not supported on the new Unified Interface introduced in the Dynamics 365 (online), version 9.0. Instead of Silverlight web resources, you must use custom controls created using the HTML web resources with HTML5 to create UI components to visualize and interact with data.

  • Share/Bookmark
Categories: Uncategorized Tags:

Dynamics 365 Data Export Service

January 16th, 2018 DynamicsMSCRM No comments

If you’ve moved to Dynamics CRM/365 Online then the likelihood is that you’ve come up against the limitation of not being able to query the SQL database directly to perform more complex reporting or for custom integrations. Many on premises deployments rely on querying the backend databases and in the past this has been a blocker to moving to the cloud – or at least it has meant a complex and costly integration to copy the data from Dynamics 365 to a on prem SQL database.
The introduction of the Data Export Service is a real game changer with the possibility to replicate your data from Dynamics CRM/365 online to an Azure SQL database in your own Azure Subscription. Once you have your data in a SQL Database you can then using PowerBI, integrate with other systems and create a data warehouse. I’ve found that the speed of the replication is impressive, being minutes/seconds and not hours.

There are a number of perquisites to enabling this which you can read about in msdn: https://technet.microsoft.com/en-us/library/mt744592.aspx
Azure Active Directory linked to Office 365
Azure SQL Database and user with correct permissions
Azure KeyVault created (using PowerShell script provided)
Dynamics CRM Online 8.1 or later
Data Export Service solution installed from App Source
Change tracking enabled for custom entities you want to sync
You must be a System Administrator to create the export profiles
The PowerShell script requires that you install the Azure cmdlets – see

https://docs.microsoft.com/en-gb/powershell/azureps-cmdlets-docs/

Here is a video that demonstrates this new service and how to set it up

Sourced From: Scott Durow (MVP)

Additional Information:
• Data Export Step by Step Manual Way: https://nishantrana.me/2017/03/19/configuring-data-export-service-in-microsoft-dynamics-365/
• Data Export Service – How to: https://crmchartguy.wordpress.com/2017/01/11/setup-the-data-export-service-with-a-power-bi-solution-template/
• Data Export Service Technet: https://technet.microsoft.com/en-us/library/mt744592.aspx#SetupAzureKV

  • Share/Bookmark
Categories: Uncategorized Tags:

SharePoint document list on main CRM form

November 21st, 2017 DynamicsMSCRM No comments
Categories: Uncategorized Tags:

D365 Editable Grids

November 1st, 2017 DynamicsMSCRM No comments
Categories: Uncategorized Tags:

Dynamics 365 Customer Center

October 6th, 2017 DynamicsMSCRM Comments off

Help and Training

  • What’s New
  • Get Started
  • eBooks & Videos
  • Admin Content
  • Share/Bookmark
Categories: Training Tags:

Creating Custom Apps using App Designer in Dynamics 365

September 28th, 2017 DynamicsMSCRM No comments
Categories: App Designer Tags:

Dynamics 365 requires TLS 1.2 or higher for connectivity beginning with the July 2017 update

September 28th, 2017 DynamicsMSCRM No comments

Starting with the July 2017 update for Dynamics 365 (online) we will begin requiring connections to customer engagement applications to utilize TLS 1.2 (or better) security. This aligns with updated Microsoft and industry security policies and best practices, and you may be required to take actions to maintain connectivity to Dynamics 365 Customer Engagement applications. Please review the following information to help you identify if you are impacted and what steps you may need to take.

What is TLS:
TLS stands for “Transport Layer Security,” and is a protocol that is an industry standard designed to protect the privacy of information communicated over the Internet. TLS is used in many web browsers and applications that communicate over HTTPS and TCP.

What is the change:
Today, all Dynamics 365 Customer Engagement online versions support TLS 1.0, 1.1 and 1.2, but starting with the release of the July 2017 update for Dynamics 365 (online), which is version 9.0 of the Customer Engagement platform, we will begin blocking connections to the updated product from clients or browsers that are using TLS 1.0 and 1.1. Versions 8.x and 7.x of Dynamics 365 Customer Engagement will not be affected with this change, and will continue to provide support for TLS 1.0, 1.1, and 1.2 as they do today. Please note: This change only affects Microsoft Dynamics 365 Online Customer Engagement, not on premises versions.

How will you or your customers be impacted:
All supported browsers for Dynamics 365 Customer Engagement (versions 7.x – Version 9.x) currently comply with the TLS 1.2 standards and will continue to work as before. However, if you have disabled the TLS 1.2 protocol on your browser or utilize a custom Windows client built with .NET 4.5.2 you will be affected and lose connectivity to organizations with the July 2017 update for Dynamics 365 (online), version 9.0.

If you have deployed a non-Windows application that connects to a Microsoft Dynamics 365 Customer Engagement instance you will need to verify that the technology stack you used supports TLS 1.2

How you or your customers can avoid being impacted.
• Custom Windows clients built utilizing .NET 4.5.2 (web and native client applications)
o Custom Windows clients built utilizing .NET 4.5.2 can be fixed by recompiling on .NET 4.6.2. Versions of .NET 4.6.2 and higher implement a process that will seek the highest possible security transport that the host operating system supports.
o If you are unable to do this, you can utilize a registry setting on Windows that will force .NET to utilize the highest possible security standard. Please Note: This is a machine-wide setting and may have undesired affects. It is recommended that you or your customer utilize the method of recompiling to .NET 4.6.2 or higher. The registry settings that will force .NET 4.5.2 to prefer TLS 1.2 machine-wide are documented in the article Microsoft Security Advisory 2960358 in the section “Suggested Actions” under “Manually disable RC4 in TLS on systems running .NET Framework 4.5/4.5.1/4.5.2″

• Non .NET Clients (web and client applications)
o Please check with the framework or language provider to determine how to configure your application to utilize TLS 1.2

  • Share/Bookmark
Categories: TLS Tags:

Dynamics Field Service, Installation and Setup

September 11th, 2017 DynamicsMSCRM Comments off

Field Serviced Installation and Setup

  • Manage your field service operations with Microsoft Dynamics 365 for Field Service
  • Install Microsoft Dynamics 365 for Field Service
  • View user accounts and security roles (Field Service)
  • Configure default settings for Dynamics 365 for Field Service
  • Turn on auto geocoding (Field Service)
  • Use Connected Field Service to remotely monitor and service customer equipment (field service)
  • Use Resource Scheduling Optimization to schedule multiple booking requirements on a recurring basis (field service)
  • Schedule anything in Dynamics 365
  • Install the Field Service mobile app
  • Share/Bookmark
Categories: Field Service Tags:

ClickDimensions: How to make changes to the service user

July 17th, 2017 DynamicsMSCRM No comments

Overview:

Describes how to change the password on the service account that was set up for ClickDimensions to communicate with CRM.

Problem/Scenario:

The ClickDimensions service requires a CRM user account to be set up as a “service account.” If the password is changed for this user, the ClickDimensions service will be unable to communicate with CRM, and you will be unable to access ClickDimensions functions from within CRM.

If you have already changed the password for the service account, when navigating to certain portions of the ClickDimensions system within CRM, you may see an error similar to “An unsecured or incorrectly secured fault was received from the other party. See the inner FaultException for the fault code and detail.” This indicates that the password is out of sync.

Resolution:

When you originally registered for the ClickDimensions solution, one of the fields you had to enter information into was the CRM user field. This information was needed to establish a service user for our application. While we recommend that you create a dedicated CRM user with a fixed password, you can easily provide any CRM user with appropriate privileges. (NOTE: Some corporate policies and security best practices dictate changing the password on service accounts and user accounts on a regular basis.)

Continue for Screen Shots and walk through of the process.

  • Share/Bookmark
Categories: ClickDimensions Tags:

ClickDimensions: How to change both the username AND password for the service user:

July 17th, 2017 DynamicsMSCRM No comments

In order to change both the username and password for the service user, you must open a support ticket. Please tell us the URL to your CRM as well as the new username. We can reset the username and then you’ll need to set the password as described in the above steps.

  • Share/Bookmark
Categories: ClickDimensions Tags:

Dynamics 365 eBooks and Videos

July 17th, 2017 DynamicsMSCRM Comments off
Categories: Dynamics 365 Tags:

ClickDimensions and CRM’s aggregate query limit

April 13th, 2016 DynamicsMSCRM No comments

CRM won’t allow you to send to a dynamic marketing list over 50,000 records. If you are CRM on prem, you can change this default number (called aggregate query limit). If you are CRM online you will need to break the sends down to lists of 50K or less.

To increase the limit, you’ll need to modify:
Database: MSCRM_CONFIG
Table: Deployment Properties
Column: AggregateQueryRecordLimit

To query the current value:

USE MSCRM_CONFIG
GO

SELECT ColumnName
, IntColumn
FROM DeploymentProperties
WHERE ColumnName = “AggregateQueryRecordLimit”

To modify the value:

UPDATE DeploymentProperties
SET IntColumn = 250000 (suggested setting)
WHERE ColumnName = “AggregateQueryRecordLimit”

  • Share/Bookmark
Categories: Uncategorized Tags:

New-AzureSBNamespace : ForbiddenError: The server failed to authenticate the request

April 13th, 2016 DynamicsMSCRM No comments

If you receive the following error below then your Azure user does not have Administrator permissions. Azure has been changing permissions, formally every users basically had admin rights however that is not the case any longer. If you are unable to add a Namespace then most likely your Azure user does not have permissions. The user will now need Administrator privileges to add a Namespace. If you have a specific Azure user that you are using for the Namespace and Queues then you will need to login to Azure with an Administrator, browse to the Service Bus area, go to Settings and then add the specific user to the Admins. Once complete you will be able to add the Namespace

  • Share/Bookmark
Categories: Azure, ClickDimensions, Uncategorized Tags:

add-azureaccount : The given key was not present in the dictionary

April 13th, 2016 DynamicsMSCRM No comments

To resolve this error the Azure Powershell instance must be October, if they have the December version it will fail. You can see the version by going to Programs and Features. They will need to uninstall the December version and install the October version, an installation overwrite will not work.

  • Share/Bookmark
Categories: Azure, ClickDimensions, Uncategorized Tags:

ClickDimensions Security Roles

February 24th, 2016 DynamicsMSCRM Comments off

During installation of the ClickDimensions solution, four security roles are created in CRM. These roles are specific to ClickDimensions and have very different purposes. The following list describes each ClickDimensions security role and its intended purpose.

ClickDimensions Core
This role should be assigned to all users (even if not using ClickDimensions). It contains the minimum set of privileges that are required by the ClickDimensions plugins and will prevent failures in creating leads/contacts and opportunities

ClickDimensions User
This security role should be assigned to users (none administrators) who view data generated by ClickDimensions. Most of the privileges are set to the Read level so the users can view the tracking data. This role also allows the user the ability to send emails.

ClickDimensions Service
This role should be assigned to the ClickDimensions service user in case the System Administrator role cannot be assigned. For more information on the required privileges for this particular user please go to the Security Requirements.

ClickDimensions Lock Email Blocks
This role should be assigned to users who need to be able to lock and unlock blocks in the Drag and Drop email editor. When a block is locked anyone without this role will not be able to edit the content of the block. More here.

  • Share/Bookmark
Categories: ClickDimensions, Uncategorized Tags:

ClickDimensions, which data center am I hosted in?

October 21st, 2015 DynamicsMSCRM No comments

To tell where your ClickDimensions account data center is deployed in, you can open the Email Template designer. The URL begins with https://app-eu.clickdimensions…, the eu in this case designates the Europe, au for Australia and us for North America.

  • Share/Bookmark
Categories: ClickDimensions Tags:

Click Dimension References

September 4th, 2015 DynamicsMSCRM No comments
Categories: ClickDimensions Tags:

Microsoft Dynamics CRM Help & Training

July 2nd, 2015 DynamicsMSCRM Comments off
Categories: Training Tags:

MS CRM Online 2015 Update 1 (7.1.0) Product Documentation is Available

May 4th, 2015 DynamicsMSCRM No comments
Categories: Uncategorized Tags: