> 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/input-management-continia.md).

# Input Management: Continia

Raptor can be integrated with Continia Document Capture, ensuring that all incoming documents are stored correctly in Raptor.

## 9A Raptor Integration Setup

Makes sure 'Enable Input Management' is on to enable the different Raptor-fields dealing with Continia on the document categories pages. It partially switches off certain Continia functionalities and uses Raptor document warehouse in replacement.

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

## Document categories

### 1. Document input

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

* Save ... in Raptor - toggle
* Raptor template for...: choose a template for the related document, attachment or mail
* Raptor Tag for Continia Documents Code
  * All documents from Continia will get this tag

### 2. Templates: template card

On the document category page go to the Customizable Colums fasttab, select the right template and edit the template card.

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

**! Do this for EVERY master template that you use.**

Most common are:

* PURCHASE master template ; type PDF
* EBILLING master template ; type XML

Go to the Code Units fasttab on this template card.

* After Step 1: fill in NAL DocMgtDocCaptureStep1 (object ID = 2057804)

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

## Register to make a purchase invoice

Attachments, invoices and emails get the Continia tags and the right template that you set up

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

## CDC document number

Every invoice you receive through Continia is given a CDC document number. This number is a unique ID for documents within Continia Document Capture.

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

This number now also appears as a tag on the Continia incoming documents.

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

### 1. Business Central: add the CDC document number to (posted) purchase invoice

9A Raptor API Setup

* EndPointAPI: Purchase invoice
* Look for the API field 'D-number'

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

9A Raptor Integration Scenarios

* Scenario: Purchase Invoice
* Link field 2057801 (NAL CDC Document No.) with the API field 'D-number'.
* Make sure you check the box in the column 'Integrate with 9A Raptor'

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

Do the same for the entity 'posted purchase invoice'

### 2. Raptor: make sure the D-number is added as a tag and field

Entity configuration: purchase invoice

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

Templates: Continia Incoming Mail, Continia Attachments, Continia Incoming Document

<figure><img src="https://1567270722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbMdBZV3cNP56k0aYYCI6%2Fuploads%2Fgit-blob-ef641159a6cce0daf27291d5af5e3a18905946bb%2Fimage%20(193).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/input-management-continia.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.
