15 Apr 15:05

AshotHambardzumyan

v1.0.4

d89629a

v1.0.4 Latest

Latest

# BUG FIXES

Fixed an issue where the cross-thread operation was invalid.
Fixed an issue where logs were not displayed properly when transferring large data.

# IMPROVEMENTS

Implemented a new matching criteria function for transferring data more flexibly and accurately.
- Attribute Matching: Introduces the ability to match records based on attribute names, allowing for precise data synchronization between D365 environments.
- Flexible Data Transfer: Offers flexible options for updating, creating, or deleting & creating records, providing users control over data between environments.

# UI CHANGES

More readable FetchXml query.
Informational logs during migration.

Assets 2

25 Nov 19:47

Hovhannes-Dilanyan

v1.0.3

615a2fd

v1.0.3

# BUG FIXES

Using the FetchXml provided by the user, if it contains an attribute top.
Using pagination properties (page & count) provided by the user in the FetchXml.
Otherwise, default values are used:
page: 1
count: 5000

# IMPROVEMENTS
# UI CHANGES

Assets 2

17 Nov 14:39

Hovhannes-Dilanyan

v1.0.2

b320d50

v1.0.2

Data Migration using FetchXml

This utility allows the user to migrate data of the entity from source to target.
The user needs to define FetchXml queries for each entity to which data should be migrated.

The utility has the following input parameters:

Source Instance – Source instance is the default instance that is connected via XRMToolBox.
Target Instance – Target instance can be selected by clicking on the Select Target Instance button.
Logs Path – Directory where the system will save the Log.txt file.
FetchXml Table – Table to add FetchXml either by typing manually or selecting a file.

For the lookup fields, the user can specify the search by name instead of searching by id. For that, it’s needed to add the SearchByPrimaryField="true" attribute in the FetchXml attribute tag.

For example

<attribute name="transactioncurrencyid" SearchByPrimaryField="true" />

Note Link entities can be used only for filtering or sorting purposes. For field values migration each FetchXml grid line should represent only one entity.

Assets 2