> 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/troubleshooting-and-known-issues/faq-1.md).

# Customer Engagement FAQ

A FAQ for the Raptor Document Warehouse integrated with Microsoft Dynamics 365 Customer Engagement, including explanations and screenshots that address the most common issues and questions.

<details>

<summary>Raptor is not available on an entity. What should I do?</summary>

This means the entity was not yet enabled in the Raptor Configuration app.\
**Solution:** Add the entity in the Entity Configurations screen in the Raptor Configuration app. See [Entity Configurations](https://docs.dynalogic.com/birds-document-warehouse-product-overview/d365-customer-engagement/entity-configurations.md)

</details>

<details>

<summary>A user gets an error when opening Raptor inside CE. How do I fix this?</summary>

The user was not added to Raptor or does not have the external system assigned.\
**Solution:** Make sure the user was created in Raptor and has the **external system** assigned.

</details>

<details>

<summary>Raptor is available on the entity, but all documents are shown and no context filter appears. Why?</summary>

This means the entity has not been configured in the Entity Configuration. Without it, no tags can be created for it.\
**Solution:** Add the entity to the **Raptor Entity Configuration**.

</details>

<details>

<summary>When dragging a document into the Raptor context, the template is not available. How do I fix this?</summary>

**Solution**: Make sure the template was created in the Raptor Configuration screen. Add a contextual tag for your data entity to ensure it's visible in the right context.

</details>


---

# 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/troubleshooting-and-known-issues/faq-1.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.
