Versions Compared

Old Version 5

changes.mady.by.user Ritchie Piessens

Saved on

compared with

New Version 6

changes.mady.by.user Ritchie Piessens

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
English

With Replica 365 you can replicate Business Central (“BC”) tables to Azure Table Storage (“ATS”). In ATS you can store large amounts of data. You can use ATS to query on this set of data using applications like Excel and PowerBI. ATS scales it’s tables automatically as your demand increases.

Replicating your BC tables to ATS will lower the impact on your BC environment, so that your BC environment is not experiencing a significant load when a lot of data is requested for reports. Because the BC data is already available in ATS, reports will also be loaded faster. From ATS you can also use the data as a source for your BI environment, for example in Azure SQL or in your Data Warehouse.

Use the Replica 365 page to configure the tables that you want to be replicated.

...

English

Prerequisites

  1. Replica 365 is succesfully configured in Business Central, using the “Replica 365 Setup page”

  2. Azure Table Storage (“ATS”) is configured (more information can be found in the article describing how to setup Replica 365.

Business Central Setup

  1. Sign in to Business Central

  2. Search for the page “Replica 365” and open this page to start entering the tables you want to replicate.

image-20240328-091938.png

  1. Start by entering the first Table you want to replicate. You can either search by name or table number.

image-20240328-095413.png

  1. Select the appropiate table. Once the table is selected, a couple of informative fields is shown and options to configure the behaviour of the replicate action

Field

Explanation

a

No. of Records

Number of records (rows) in the table

b

Fields

Number of selected fields in the table. Click on the field to open the Field Selector.

Replica supports up to 250 fields for each destination table, due to limitations of ATS. ATS supports a maximum of 255 fields, 5 are needed for system properties. When your table contains more than 250 fields you need to make a subselection within the existing columns or replicate the table in multiple parts.

image-20240328-125550.png

c

Exclude Flowfields

When flow fields ("calculated fields") are excluded, a replication action will be faster. For large tables, you can choose to replicate the table in multiple parts, each with part of the flow fields.

d

Replication Type

Choose between [Full] and [Changes].

[Full] will replicate the table in full for each replication round.

[Changes] will only replicate the changed records compared to the previous replication. This is determined using the attribute "Last Modified Date Time" of the selected table.

Warning: when you change the Replication Type from [Changes] to [Full], this will result in an entire new copy of the table “as is” at that moment. This results in losing history in ATS, handle this with care

image-20240328-125409.png

e

Full Sync Required

When you change the selected fields, for example (de)select Fields, this will trigger a Full Sync the next replication round. This is necessary to keep the number of fields per row in ATS consistent.

Warning: This results in losing history in ATS. All records that do not longer exist in BC, will no longer be available in ATS. Handle this with care.

f

Track Deletes

Check this field when you want Records that are deleted Records in BC to be marked “as deleted” in ATS.

If this option is not checked, deleted Records in BC

The field “DeletedAt” in ATS will be updated with the DateTime of Deletion in BC (not the DateTIme of updating the record in ATS).

When combined with

Warning: When [Replication Type] “Changes” Enabling “Track Deletes”

when you changes in combinatie met track deletes

g

No. of Deleted Records

h

Status

i

Start

j

Duration

k

Unprocessed Messages

l

No. of Errors

Select fields

Best practices