---
title: "Replicated Test Data Example - Test and Performance Suite Guide"
slug: "replicated-test-data-example"
description: "This example shows a list of sales orders that have been generated based on the following settings. Read the article for more information."
updated: 2026-03-03T14:35:52Z
published: 2026-03-03T14:35:52Z
canonical: "kb.lasernetgroup.com/replicated-test-data-example"
---

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

# Replicated Test Data Example

This example shows a list of sales orders that have been generated based on the following settings:

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image (84).png)

Here we can see the expected 20 sales orders:

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image (85)(1).png)

The original sales order had ten sales order lines, therefore, each one of these sales orders has 20 sales order lines, as the **Lines multiplier** was set to **2**.

> [!NOTE]
> Note
> 
> The journal records may not be created depending on your Dynamics 365 FO setup. For example, these error messages may be displayed when trying to create a sales order confirmation journal or a delivery note for the sales order:
> 
> ![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image (86)(1).png)These error messages are displayed because Dynamics 365 FO has been configured in a way that requires order holds to be approved before a sales order confirmation and delivery note can be posted.
> 
> In these cases, a UX test may be a better approach to creating the data as a UX test can be used to create a sales order, approve the order hold, then post and print the sales order confirmation and delivery note. Consult the [Create a UX test from the Task recorder](/v1/docs/create-a-ux-test) section of this guide for more information.