---
title: "Set up Staging journal connector"
slug: "set-up-staging-journal-connector"
tags: ["Task topic"]
updated: 2026-03-20T07:38:41Z
published: 2026-03-20T17:44:08Z
canonical: "docs.staedean.com/set-up-staging-journal-connector"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.staedean.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Set up Staging journal connector

Set up a connector of type **Staging journal**. Use this type to validate and approve data before it is imported into D365 F&SCM.

A staging journal scenario consists of:

- A message to import the data from the source into the staging journal. This message has a target document of type **Staging** and a target connector of type **Staging journal**.
- A staging journal which is an additional table in which the data is validated and approved before the data is imported into D365 F&SCM.
- A message to get the approved data from the staging journal and import it into D365 F&SCM. This message has a source document of type **Staging** and a source connector of type **Staging journal**.

### Steps

1. Click **Connectivity studio - Integration Design**.
2. Click the **Connectors** tab.
3. Click **New**.
4. In the **Connector** field, type a value.

> [!NOTE]
> **Note**
> 
> You are advised to not include, in the connector name, the name of the application to which you connect. Use the **Application** field to define the applicable application for the connector.
5. In the **Project** field, enter or select a value.
6. Define the applicable application for the connector. For a staging journal connector, for example, select a 'Staging' or 'D365 F&SCM' application.

In the **Application** field, enter or select a value.

> [!NOTE]
> **Note**
> 
> - You can only select an application that is defined for the applicable project. You can define project applications on the **Projects** page.
> - You can type any existing application name, whether it is defined as project application or not. If the typed application is not defined as project application, it is automatically added to the project applications.
7. In the **Connector type** field, select '**Staging journal**'.
8. Sub-task: Set properties.
  1. Define the target company for the connector.

If you want to use the active company as the target company, do not define a target company. As a result, the company from which a message is run is used as the target company.

In the **Target company** field, enter or select a value.
  2. If the connector is used on a message to get the approved data from the staging journal and import it into D365 F&SCM, you can limit the considered data to the current company only. So, only the staging journal records for the current company are taken from the staging journal and imported into D365 F&SCM.

Select **Yes** in the **Company only** field.
9. Sub-task: Select custom handler.
  1. Expand the **Custom** section.
  2. For a **Staging journal** type connector, the standard handler class is **BisConnectorStagingJournal**. This handler class exports data from or imports data into a staging journal.

You can use a customized handler class. To do so, extend the standard handler class.

In the **Handler** field, you can enter or select a custom handler class.
10. Sub-task: Define source companies.
  1. Define the source companies for the connector.

You can define the source company for a connector in these ways:

Expand the **Source companies** section.
    - One specific source company.
    - Several source companies.
    - No source company: Do not define a source company if you want to use the active company as the source company. As a result, the company from which a message is run is used as the source company.
  2. Click **New**.
  3. In the **Company accounts ID** field, enter or select a value.
11. Sub-task: Set advanced options.
  1. Expand the **Advanced options** section.
  2. A document can have a query for which cross-company is enabled. If a user, with access to a restricted set of companies, runs a message that uses the document, the cross-company option does not work. If you have this scenario, make sure the cross-company option is enabled for the used connector. Otherwise, you can disable the cross-company option.

Select **Yes** in the **Cross company disabled** field.
12. Close the page.

> [!NOTE]
> **Notes**
> 
> - You can change the type of an existing connector. If you do so, also fill in the applicable fields. For more information, refer to the topic about the setup of the newly chosen connector type.
> - The environment type does not apply to a **Staging journal** connector.

## Related

- [Staging - Connectivity Studio](/staging-concept.md)
- [Staging journal statuses - Connectivity Studio](/staging-journal-statuses.md)
- [Customize staging tables - Connectivity Studio](/customize-staging-tables-concept.md)
- [Customize connector handler class](/customize-connector-handler-class.md)