MyRapidi
MyRapidi
Menu

Search our Wiki

MS Dynamics CRM

Microsoft Dynamics CRM can be run in three different configurations:

  1. Locally installed (OnPremise - at your site)
  2. Partner hosted (using IFD authentication)
  3. Windows Live / Online (Cloud / OnDemand)
  4. Azure Portal
  5. Microsoft Office Portal

As the configuration is a bit different for each of those configurations, we will explain them separately in the next sections.

The following versions of MS Dynamics CRM are supported

  • MS Dynamics CRM 4.0
  • MS Dynamics CRM 2011
  • MS Dynamics CRM 2013
  • MS Dynamics CRM 2015
  • MS Dynamics 365 Sales

MS CRM locally installed (OnPremise)

If your MS Dynamics CRM is installed locally at your site, you need to install a RapidiConnector so that Rapidi can access your MS Dynamics CRM:

show informationhide information
Installing the RapidiConnector

The fields on the MS Dynamics CRM Data Source Card are set up as follows:

  • Description: Enter a text describing the Connection.
  • Authentication Type: Select "Local network"
  • Server URL: Specify the URL to the MS Dynamics CRM instance. For example: http://192.168.191.120:5555/ or  crm.mydomain.com or for CRM2015
    http://mycrmserver/orgname/XRMServices/2011/Organization.svc/web
  • Organization Name: Specify the name of your organization. For example: MicrosoftCRM  or  MyCompany
  • User ID: Specify the Userid. For example: Administrator
  • Password: Specify the password for the above userid.
  • Domain: Specify the domain name. For example: LITWAREINC
  • STSEndpoint/URN: not used

MS Dynamics CRM partner-hosted (using IFD)

If your MS Dynamics CRM is installed at a hosting provider and this hosting provider supports IFD, then use the following setup. If the hosting partner does not support IFD and they are willing to install the RapidiConnector in their network, you can also use the "locally installed" setup.

When using IFD for Authentication, then all communication is going directly from RapidiOnline servers to/from the hosting partner. So in this case you don't need a local RapidiConnector.

Instead of downloading and installing the RapidiConnector, please use the "Delete" button below the RapidiConnector to remove the RapidiConnector from the Connection before continuing with the setup.

The fields on the MS Dynamics CRM Connection are set up as follows:

  • Description: Enter a text describing the Connection.
  • Authentication Type: Select "IFD"
  • Server URL: Specify the URL to the MS Dynamics CRM instance. For example: mycompany.crmhost.dk
  • Organization Name: Specify the name of your organization. For example: MyCompany
  • User ID: Specify the Userid. For example: Administrator
  • Password: Specify the password for the above userid.
  • Domain: not used, you can leave it blank
  • STSEndpoint/URN: not used

MS Dynamics CRM Windows Live / Online

If your MS Dynamics CRM is run by Microsoft in the Windows Live or Online Cloud, then use the following setup.

When using Windows Online for Authentication, then all communication is going directly from Rapidi servers to/from the Microsoft Online Servers. So in this case you don't need a local RapidiConnector.

Instead of downloading and installing the RapidiConnector, please use the "Delete RapidiConnector" button to remove the RapidiConnector from the Connection before continuing with the setup.

The fields on the MS Dynamics CRM Connection are set up as follows:

  • Description: Enter a text describing the Connection.
  • Authentication Type: Select "Windows Live"
  • Server URL: Specify the URL to the MS Dynamics CRM instance. For example mycompany.crm.dynamics.com - for Europe it would be mycompany.crm4.dynamics.com (this is only used to get to the correct discovery service - e.g. dev.crm4.dynamics.com for Europe).
  • Organization Name: Specify the name of your organization. For example 'MyCompany'. This can be either the unique CRM organization name (found under Settings, Customization, Developer Resources and copy the value found under the first entry, "Organization Unique Name") or you can use the organization Friendly Name (and we will look up the unique name using the discovery service). We recommend using the Friendly Name.
  • User ID: Specify the Userid. For example: myname@msn.com
  • Password: Specify the password for the above userid.
  • Domain: not used, you can leave it blank
  • STSEndpoint/URN: When testing the connection RapidiOnline will output a text string to fill into this field. Something like "https://login.microsoftonline.com/RST2.srf#urn:crmna:dynamics.com". Entering this string here will greatly reduce the login time as we can skip going to the discovery service to get this information. Leave the field blank until you see a message from Rapidi, saying exactly what to fill in.

Azure Portal

In order to configure the below steps you need to have an Azure admin user account.

  1. Log in to portal.azure.com
  2. Go to Azure Active Directory
  3. Go to App Registrations
  4. Click + New registration
    • Name = [your App Name] (Example: RapidiCRMApp)
    • [Section] Supported account types > Select :  ... Single tenant
    • Click Register
  5. Within the same screen
    • On the API permissions page for your app, click the 'Add a Permission' button.
    • Make sure the Microsoft APIs tab is selected. In the Commonly Used Microsoft APIs section, click on the Dynamics CRM and select Delegated permissions.
    • Ensure that the following permissions are checked:
      • User_impersonation (Access Common Data Service as organization users)
    • Click the Add permissions button.
    • You will be returned to the previous screen, and there you have to click Grant Admin Consent for ....
  6. Within same screen, From the Certificates & secrets page, in the Client secrets section, choose New client secret:
    • Type a key description (for instance app secret),
    • Select a key duration of either In 1 year, In 2 years, or Never Expires.
    • When you press the 'Add' button, the key value will be (only once) displayed, copy, and save the value in a safe location.
  7. Keep the Application Id and the Application secret in a safe location, we will need these later.

Microsoft Office Portal

1. Login to Power Platform Admin Center portal, e.g.: https://admin.powerplatform.microsoft.com

2. From the left Menu, choose Environments

3. Choose your CRM Environment (for example rapidionline.com default environment)

4. Click to open the CRM Environment

5. Choose Settings located at the top of the page and then

6. Choose Users + Permissions and navigate to Application users

7. Choose +New app user located at the top.

8. A side window will open. In this side window Click +Add an app then choose the app id created in Azure (Check the first step of this document) and click Add

9. Choose the Business Unit from the options below (usually it is the CRM org)

10. Click on the Pencil Icon on the right to add a Security Role to the Application for the selected Business Unit then click Save and finally click Create

11. Congratulations, you have completed the setup.

Configuration in Rapidi

  1. Login to MyRapidi. Navigate to the Connections page and create a new connection of type CRMODATA.

    The fields of the CRMODATA Connection are as follows:
    • Code: auto-populated
    • Description: - type a proper description (Example: Connection to CRM TEST Environment)
    • Authentication Type: Oauth2 (Azure AD)
    • Server Connect: Here paste the Url from CRM environment, example: https://domainname.crm4.dynamics.com/xxxxx

      • Note that the URL from the client could be larger but you’ll need to chop it until ‘dynamics.com’ and then add ‘/api/data/v9.0/accounts’. The full server connect URL should look like this: https://domainname.crm4.dynamics.com/api/data/v9.0/accounts

    • Company: Enter Company Name (or leave it blank)
    • User Id: This is the Azure application Id (that was created in the first step)
    • Password: This is the client secret/application secret (created on the first step)
    • Domain: This is the tenant id of the customer (can be found under Azure)
    • Resource: https://domainname.crm4.dynamics.com/
    • Metadata URL: copy from the Server Connect and remove the last /accounts and add /$metadata. The full metadata URL should look like this:
      https://domainname.crm4.dynamics.com/api/data/v9.0/$metadata
    • Use SSL: Mark it as True

Copy, Test, Activate Changes and Read Design

show informationhide information
Copy Connection

show informationhide information
Connection Test

show informationhide information
Activate Changes

show informationhide information
Read Design