---
title: "Pull master data with dynamic button"
slug: "pull-master-data-with-dynamic-button"
description: "Learn how to pull master data, like vendor groups, from a source company using a dynamic button in your target company’s data management system."
tags: ["Task topic"]
updated: 2026-03-20T11:15:15Z
published: 2026-03-20T17:44:34Z
canonical: "docs.staedean.com/pull-master-data-with-dynamic-button"
---

> ## 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.

# Pull master data with dynamic button

In the target company, as a data steward, you can use a dynamic button to pull master data from the source company.

From which pages you can use the dynamic button is defined by the dynamic button setup.

### Steps

1. Open a page for which the dynamic button is set up.

In the steps, as an example, you want to create a vendor account. The desired vendor group does not exist in your company. However, the vendor group exists in the source company. You pull the desired vendor group master data from the source company.

Go to **Accounts payable** > **Vendors** > **All vendors**.
2. On the **Action Pane**, click **Master data management**.
3. Click **Pull vendor groups**.
4. In the list, find and select the desired vendor group.

> [!NOTE]
> **Note**
> 
> You can only pull a record to the target company for which a master data record exists in the source company.
5. Click **Pull master data**.
6. Define which status the pulled record must get in the master data record subscriptions.

The status of a new subscription cannot be higher than the master data record status.

If you set the **Master data status** field to:

On the dialog, in the **Master data status** field, select an option.

> [!NOTE]
> **Note**
> 
> If the selected status is higher than the master data record status, a warning message is shown.
  - **New**, the master data subscription status is set to **New**.
  - **Approved**, the master data subscription status is set to **Approved**. However, if the master data record status is **New**, the subscription status is set to **New**.
  - **Released**, the subscription status is set to **Released**. However, if the master data record status is:
    - **Approved**, the subscription status is set to **Approved**.
    - **New**, the subscription status is set to **New**.
7. If you set the **Master data status** field to **Released**, you can define a planned release date.

This date defines when the pulled master data record is released to the target company.

In the **Planned release date** field, enter a date and time.

> [!NOTE]
> **Note**
> 
> The master data record only is released if, in the source company, the master data record status is **Released**.
8. If you set the **Master data status** field to **Released**, you can send the master data record immediately to the target company.

Select **Yes** in the **Send master data** field.

> [!NOTE]
> **Note**
> 
> The master data record only is sent immediately if, in the source company, the master data record status is **Released**.
9. Click **OK**.
10. Close the page.

> [!NOTE]
> **Notes**
> 
> You only can pull master data to the current company if a master data entity exists that has a message with:
> 
> - The current company as the target company.
> - A target group to which the current company belongs.
> - An organization hierarchy in which the current company is a child company of source company from which you want to pull master data.

## Related

- [Use organization hierarchies for master data distribution](/use-organization-hierarchies-for-master-data-distribution.md)
- [Pull master data](/pull-master-data-flow.md)