Raptor Document Warehouse
  • Welcome
  • 🦖Raptor Document Warehouse
    • User guide
      • The layout of document warehouse
      • Tenant settings
      • Uploading files
      • Mail a file
      • Search for a file
    • Configuration
      • Security
      • Users
      • Fields
      • Templates
      • Taxonomy
      • External Systems
      • Jobs
        • D365-FO Sync Job
        • SQL Sync Job
      • Document triggers
      • Storage providers
      • Entity Configuration
  • 🔗Integrations
    • D365 Finance & Operations
      • 9A Raptor DWH Parameters
        • General
        • Document management
        • Output management
        • E-Platform management
      • Document Management
        • Security & permissions
        • Feature flags
        • Standard document management
      • Input Management
      • Output Management
      • Process Management
      • Inquiries and reports
      • Troubleshooting
    • D365 Customer Engagement
      • Set up Raptor credentials
      • Sync Taxonomy
      • Output Management
      • Raptor Users
      • Record merging
    • D365 Business Central
      • Installation of Raptor in BC
      • Configuration Raptor - BC
      • How to load the kickstart
      • 9A Raptor Pages in BC
      • Input Management
      • Document Sending Profiles
  • 🐦EDI
    • E-Platform
      • Concepts
      • Babelway & Peppol
      • Best Practices
      • Security / Authentication
      • Deep Dives
        • About Transformations
        • Kofax integration
  • 👨‍💻developers
    • API starting guide
    • Embedding Raptor
    • D365 Finance & Operations
      • Document Management
      • Output Management
      • Input Management
  • 🚀Releases
    • Raptor Document Warehouse
    • D365 Finance & Operations
Powered by GitBook
On this page
  1. Raptor Document Warehouse
  2. Configuration
  3. Jobs

D365-FO Sync Job

PreviousJobsNextSQL Sync Job

Last updated 3 months ago

An example of the D365-FO sync job requires a lot of configuration.

Top level, it looks like this:

We can see the generic parts at the top. Like: job type, cron schedule, run-as user, and the job history (at the bottom).

There are however also some job specific parameters.

The delta packager for example: this is an ID (which is currently shared by all the tenants on the same environment). You can just copy it from another tenant when creating a new D365-FO sync job.

The OAuth Settings define the parameters required to authenticate with a D365-FO service.

Here you need to specify the url to the active directory tenant that has the Client App ID, and of course also the client app id itself, and the related secret. And finial the URL to the D365-FO environment. Be carefull not to include a trailing slash ‘/’ at the end (!) since that won’t work.

Remark: the client application ID should be configured in the FO environment as well, it should also be linked to a system user that has the necessary user rights, and in the Azure portal the application should also be linked to some access rights.

The Delta Fetch Settings holds the details of what exactly should be retrieved after we are authenticated, and how long we should store that information.

In this example, we have created a package in FO with the RAPTOR_CONTEXT, and call it using key D365FO_DELTA_PACKAGE. We request this info for the USMF legal entity, and keep the result for 30 days. Not correctly configured in the screenshot here is the URL we should be identical to the Azure Resource field as found in the OAuth Settings.

The screenshot below shows the counterpart of this configuration in FO.

In the Delta Storage Settings we define the Azure blob storage account used to store the exported package temporary. This is required in case the jobs fails, so it can be continued without us having to fetch the package again. (That is not even be possible if the package contains tables with an incremental push strategy.)

We create an azure storage account for each customer. It will also automatically take over the storage account details from another job, if there is already another job that has a storage account configured in the tenant.

🦖