> For the complete documentation index, see [llms.txt](https://docs.dynalogic.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dynalogic.com/birds-document-warehouse-product-overview/d365-business-central/set-up-integration-raptor-bc.md).

# Set up integration Raptor - BC

On this page you can find how to set up the link between Raptor and Business Central. This requires configuration in both Raptor and Business Central.

## Raptor setup: configuration

Go to <https://raptor.9altitudes.com>

### 1. Add Business Central as an external system

Configuration -> external systems -> add an external system (BC)

<figure><img src="https://1567270722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbMdBZV3cNP56k0aYYCI6%2Fuploads%2Fgit-blob-8fad183e9e05907b00a04555a6089c3ed1021968%2Fmsedge_nifh94LkL8%20(1).png?alt=media" alt=""><figcaption></figcaption></figure>

* make sure the 'Public'-toggle is on

Add the ID and secret to your password manager

* These are application keys, **and you will see them only now (!) so save them to your password manager**
* Once you have created the system, you must add at least one user to the system.
* Important note: button ‘Renew secrets’ : use this ONLY when the secret is compromised

### 2. Set up the Raptor users

Make sure to do this for every user

<figure><img src="https://1567270722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbMdBZV3cNP56k0aYYCI6%2Fuploads%2Fgit-blob-237f731a70076eca915f3fe6e20881bfa7767013%2Fmsedge_gBO0zF4t0U.png?alt=media" alt=""><figcaption></figcaption></figure>

* Step 1 - 3: add a user
* Step 4: fill in the general information
  * Make sure to use the email address linked to the BC environment
* Step 5: switch the 'Enabled' toggle on
  * Note: we do not remove users, because we always need the reference so we can show information about i.e.: the uploader of a document. A disabled user will not be able to login to the UI, or get any data from the API gateway
* Step 6: add one or more roles
  * Basic = default role that is added automatically to a new user
  * You can also assign the administrator role
* Step 7: assign at least one external system to the user
  * In this case: assign BC as an external system
  * This is the system you want the user to be able to access Raptor directly from within that system

## Check Azure App Registration

Note: the set up is normally already done by a technical, so you just need to check it

Go to <https://entra.microsoft.com>

### 1. Check the application ID

<figure><img src="https://1567270722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbMdBZV3cNP56k0aYYCI6%2Fuploads%2Fgit-blob-e3374dc0f2b60f94a8686352808a5edb768a82bb%2Fimage%20(117).png?alt=media" alt=""><figcaption></figcaption></figure>

### 2. Check API permissions

<figure><img src="https://1567270722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbMdBZV3cNP56k0aYYCI6%2Fuploads%2Fgit-blob-82dc65dfc01b63735d8ec92397e2f4bb25dcf815%2Fimage%20(118).png?alt=media" alt=""><figcaption></figcaption></figure>

This normally happens automatically

API permissions should include

* API.ReadWrite.All (= access to APIs and webservices)
* Automation.ReadWrite.All (= full access to automation)

## BC setup: configuration

### 1. User permissions

Users - page -> User Card -> User Permission Sets (FastTab)

Make sure the following permission sets are delegated to the user

* NAL Raptor Core
* NAL Raptor Email
* NAL Raptor Output

<figure><img src="https://1567270722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbMdBZV3cNP56k0aYYCI6%2Fuploads%2Fgit-blob-4a53fb5136911054a4fbb4b9a01774d2aabe346d%2Fimage%20(120).png?alt=media" alt=""><figcaption></figcaption></figure>

### 2. 9A Raptor Integration Setup

9A Raptor Integration Setup - page -> General FastTab

* System ID: enter the ID of your external system
* Secret: Azure app registration secret (technical who does the onboarding will provide this in the password manager)
* URL: <https://raptor.9altitudes.com>
  * Make sure it is always this URL *(Not: raptor.adultima.com)*
* Active: toggle on will automatically be triggered when the setup is completed

<figure><img src="https://1567270722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbMdBZV3cNP56k0aYYCI6%2Fuploads%2Fgit-blob-8eae92fdb0f98c38d3866626b4dbb9c2211e2544%2Fimage%20(106).png?alt=media" alt=""><figcaption></figcaption></figure>

### 3. Set up the Microsoft Entra Application

Microsoft Entra Application - page

* Client ID = Azure Application ID
* Make sure the user permissions sets are set up as in the following image

<figure><img src="https://1567270722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbMdBZV3cNP56k0aYYCI6%2Fuploads%2Fgit-blob-eddaf1815eeb397c92a4f25753f5e6f0470d2f41%2Fimage%20(72).png?alt=media" alt=""><figcaption></figcaption></figure>

* To successfully perform the taxonomy job, you sometimes need the SUPER (DATA) permission.

### 4. Test connection

9A Raptor Integration Setup - page

* Click on the ‘Test Connection’-action
* When the connection failed, make sure to run through the steps again about the setup (in Raptor and BC)

<figure><img src="https://1567270722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbMdBZV3cNP56k0aYYCI6%2Fuploads%2Fgit-blob-a5a99859559cb36982c084863aac9733537b8913%2Fx7rU2ZCoan.png?alt=media" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.dynalogic.com/birds-document-warehouse-product-overview/d365-business-central/set-up-integration-raptor-bc.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
