> For the complete documentation index, see [llms.txt](https://docs.solutioo.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.solutioo.de/datanorm-item-import/datanorm_en_us/getting-started/installation-and-licence.md).

# Installation and Licence

Marketplace installation, licence validation and validity.

## Installation

The app ships as an extension for Microsoft Dynamics 365 Business Central and is installed from the marketplace.

{% stepper %}
{% step %}

#### Find the extension

In Business Central open **Extension Management** and choose **Marketplace**. Search for **DATANORM Item Import**.
{% endstep %}

{% step %}

#### Install

Installation creates the tables, pages and permission sets. No tenant restart is required.
{% endstep %}

{% step %}

#### Assign permissions

Give your users one of the three permission sets, see [User Roles & Permissions](https://docs.solutioo.de/datanorm-item-import/datanorm_en_us/getting-started/user-roles-and-permissions.md).
{% endstep %}

{% step %}

#### Configure

Continue with the [Setup Wizard](https://docs.solutioo.de/datanorm-item-import/datanorm_en_us/getting-started/setup-wizard.md).
{% endstep %}
{% endstepper %}

{% hint style="info" %}
Always trial a first import in a sandbox environment. An article import changes master data, and a full catalogue can create several thousand items.
{% endhint %}

## Licence

The app is obtained and licensed through **Microsoft AppSource**. The term follows your AppSource subscription and is managed through Microsoft. Nothing needs to be configured or entered inside the app.

### Trial and sandbox builds

If you receive the app directly from solutioo for evaluation instead of taking it from AppSource, that build carries a fixed expiry date. Its status is then shown in **DATANORM Setup**.

<table><thead><tr><th width="260">State</th><th>Behaviour</th></tr></thead><tbody><tr><td>Valid</td><td>All features are available. The status shows the expiry date.</td></tr><tr><td>Expiring within 14 days</td><td>A notice appears with the number of days remaining.</td></tr><tr><td>Expired</td><td>Import and synchronisation stop with a message. Data already imported stays intact.</td></tr></tbody></table>

{% hint style="info" %}
This expiry date applies only to trial and sandbox builds handed over directly. An installation taken from AppSource does not carry it.
{% endhint %}

{% hint style="warning" %}
An expired trial blocks importing but deletes nothing. After moving to the AppSource version you carry on without any rework.
{% endhint %}

To extend a trial period, get in touch using the details under [Support Contacts](https://docs.solutioo.de/datanorm-item-import/datanorm_en_us/operations-and-troubleshooting/support.md).


---

# 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.solutioo.de/datanorm-item-import/datanorm_en_us/getting-started/installation-and-licence.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.
