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
        • D365FO Taxonomy
        • SQL Taxonomy 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
        • Standard document management
      • Feature flags
      • 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
      • Process Management
    • SharePoint Storage Provider
  • 🚀Releases
    • Raptor Document Warehouse
    • D365 Finance & Operations
Powered by GitBook
On this page
  1. Raptor Document Warehouse
  2. Configuration
  3. Jobs

D365FO Taxonomy

PreviousJobsNextSQL Taxonomy Job

Last updated 28 days ago

The D365FO Taxonomy job retrieves masterdata from Dynamics 365 F&O using an export project in it's . Raptor will retrieve the export created by F&O and generate tags from it using the Entity Configuration. Taxonomy jobs are useful to proactively create tags that might be useful for Raptor users.

In most cases, Raptor integrations are capable of making tags ad-hoc, whenever they are needed. Taxonomy jobs are therefore not essential for a working production environment. Their primary purpose is to make tags available for manual search in Raptor.

D365FO Taxonomy jobs use a Source service connection to a Dynamics 365 F&O environment (see ) and use the Default delta packager.

Delta Fetch settings

To create a D365F&O Taxonomy job, an Export project must be available in your Dynamics 365 F&O environment. The export project can contains the list of entities that you wish to create tags for in Raptor. Be sure to choose 'XML-element' as source data format for each entity.

Note that tags will not be created for an entity if there is no Entity Configuration set up for it.

Uri: the URL of your F&O environment (e.g. https://finopsaos.cloudax.dynamics.com).

Definition Group Id: Group name of the export project

Package name: the name given to the created exports

Legal Entity: the legal entity in F&O which the export should be made for

Retention Days: amount of days that the export should remain available

Set the default refresh type for each entity to 'Incremental push only' to prevent unnecessary load on your F&O environment and Raptor tenant. Incremental push requires activating on the entity.

🦖
change tracking
Data Management functionality
Service connections