Skip to main content

Building pipelines with Microsoft Dynamics 365 Reader

In Striim, an app (application) holds the details of the data pipeline—source & target details and other logical components organized into one or more flows. Developing an application also means building the data pipeline.

You can create applications:

Pre-requisite - The initial setup and configuration you do in Microsoft Dynamics 365 applications are described in the Initial setup section.

Create a Dynamics 365 Reader application using the Flow Designer

This procedure outlines how to use Striim’s Flow Designer to build and configure data pipelines. Flow Designer enables you to visually create applications with minimal or no coding.

  1. Go to the Apps page in the Striim UI and click Start from scratch.

  2. Provide the Name and Namespace for your app. The namespace helps organize related apps.

  3. In the component section, expand Sources, and enter a keyword such as Dynamics 365 Reader in the search field to filter available sources.

  4. Select the desired source (Microsoft Dynamics 365).

  5. In the properties panel, provide the properties for the reader.

    ms-dynamics-365-reader.png

  6. Click Save to complete the properties configuration.

  7. You can drag and drop processors, enrichers, and targets to complete your pipeline logic.

  8. Once done, deploy and start the application to begin data flow.

Create a Dynamics 365 Reader application using TQL

The following sample TQL uses Striim’s Dynamics 365 Reader to read from the Sales Edition.

 CREATE SOURCE SourceName USING Global.MicrosoftDynamics365Reader (
    PollingInterval: '5m',
    ClientSecret: '<ClientSecret>',
    RefreshToken: '<RefreshToken>',
    TenantId: 'TenantID',
    AdfsServer: '',
    startPosition: '%=-1',
    Tables: '%',
    ClientId: 'ClientId',
    ConnectionPoolSize: 20,
    connectionProfileName: '',
    FetchSize: 5000,
    ConnectionTimeout: '300',
    Edition: 'Sales',
    Mode: 'Automated',
    useConnectionProfile: false,
    IncrementalLoadMarker: 'ModifiedOn',
    OrganizationUrl: 'URL',
    MigrateSchema: true,
    ThreadPoolCount: 10
  )
  OUTPUT TO DataStream;