MyRapidi
MyRapidi

Search our Wiki

MS Dynamics AX ODATA

Microsoft Dynamics 365 for Finance & Operations OData (MS Dynamics AX)

Support for MS Dynamics AX using OData. Both reading data and writing (insert and update) is supported.

We support both OnPremise and Azure-based installations and also Microsoft-hosted (Dynamics 365 online) deployments.

The following versions of MS Dynamics AX are supported

  • Microsoft Dynamics 365 for Finance
  • Microsoft Dynamics 365 for Finance & Operations (MS Dynamics AX 2018)
  • older version - please contact us.

Additional installation (only for local installations or if you control the Azure instance)

show informationhide information
Installing the RapidiConnector

Please Note: The OData Connection is by default created with an attached RapidiConnector. If you don't need the RapidiConnector - if you want Rapidi to connect directly to your OData system - you need to delete the RapidiConnector from the Connection (click the trashcan icon (Delete RapidiConnector) all the way to the right on the RapidiConnector header). 

Configuration

Below is a description of the fields on the Connection:

  • Code: The unique code for this connection (cannot be changed)
  • Description: Enter a text describing the Connection.
  • Authentication Type: Choose howto authenticate with your MS Dynamics 365 system. Normally you would choose "OAuth2 (Azure AD)" here and specify the connection parameters and credentials as described below.
  • Server Connect: Specify the full path to your Dynamics 365 EE system - like "https://testing123.cloudax.dynamics.com/data/Customers"
  • Company: Specify the AX company that this connection should use - like "usmf". You need to create a Connection for each Company in AX that you want to read or write data from/to. Rapidi will automatically handle to filter and specify the Company when sending data and requests to AX (so you don't need to worry about setting the dataAreaId).
  • UserID: Here you specify the userid (credentials) to access your Dynamics 365. When using the OAuth2 authentication, this is the ApplicationID of the App created in the Azure AD.
  • Password: Here you specify the Password corresponding to the above UserID. For OAuth2, this is the Key found on the App created in the Azure AD.
  • Domain: The Domain for Authentication. For OAuth2, this is the Tenant ID of your Azure AD.
  • Resource: This field is only used for OAuth2 authentication. Specify here the resource (the Application ID of the App in your Azure AD that you want to have access to - e.g. your Dynamics 365 EE system).
  • Metadata URL: Here you can specify the URL to the metadata for your Dynamics 365 EE - like "https://testing123.cloudax.dynamics.com/data/$metadata"
  • Use SSL: Check this field if the connection should use SSL (this setting dictates if SSL is used independently of specifying http or https above).

 

Configuration in Azure Portal

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

  1. Login to portal.azure.com
  2. Go to Azure Active Directory
  3. Go to App Registrations
  4. Click + New registration
    • Name = [your App Name] (Example: RapidiApp)
    • [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 ERP and select Delegated permissions.
    • Ensure that the following permissions are checked:
      • - AX.FullAccess
      • - Odata.FullAccess
    • Click the Add permissions button.
    • You will be returned to the previous screen, and there you have to click Grant Admin Consent for .... click there.
  6. Within the same screen, From the Certificates & secrets page, in the Client secrets section, choose New client secret:
    • Type a key description (of 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.

Configuration in Dynamics 365 Finance & Operations

Note: To complete below steps you need to have a D365 Finance & Operations user account
  1. Login to your D365 Finance & Operations
  2. Choose from the Navigation Pane (the Menu from left side)
  3. Go to System Administration
  4. Click Setup
  5. Click Azure Active Directory Applications
  6. Click New

Optionally, you can directly navigate to the Azure Active Directory Applications from the search box, e.g. search for Azure Active Directory Applications and the following screen will appear:

Click New For Client ID– paste the Application Id from Azure (the one that you created earlier) Give it a Name (ex. RapidiApp) Under User Id – choose the user to whom this app should be running (select a user that has read & write permissions at least) Click Save

After you have successfully created the Client Id within D365 Finance & Operations - please copy the current URL from the browser and save it in a safe location. This will be used for setting up the connection within MyRapidi platform (the Azure tenant id will be needed as well).

Configuration in Rapidi

  1. Login to MyRapidi. Go to the 'Connections' page and choose MS Dynamics 365 FO (AX) OData
  2. The fields of the MS Dynamics 365 FO (AX) OData Connection are as follows:
    • Code: auto-populated
    • Description: – type a proper description
    • Authentication Type: Oauth2 (Azure AD)
    • Server Connect: Here paste the Url provided by the customer (URL from F&O environment), for example, https://demodynfo81d5be6810de336c13aos.cloudax.dynamics.com/data/Customers?cross-company=true Note that the URL from the client could be larger but you’ll need to chop it until ‘dynamics.com’ and then add ‘/data/Customers?cross-company=true’
    • Company: Enter Company Name
    • User Id: This is the application Id (that was created in the first step)
    • Password: This is the client secret/application secret (created in the first step)
    • Domain: This is the tenant id of the customer
    • Resource: Enter https://demodynfo81d5be6810de336c13aos.cloudax.dynamics.com
    • Metadata URL: copy from the Server Connect and modify it a bit (remove everything after dynamics.com/data/ and add $metadata), please see below: https://demodynfo81d5be6810de336c13aos.cloudax.dynamics.com/data/$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