> For the complete documentation index, see [llms.txt](https://docs.inogic.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inogic.com/backup4dynamics/restore/preserve-system-fields.md).

# Preserve System Fields

Backup4Dynamics provides an option to preserve the original Modified On and Modified By field values of a record during restore in Microsoft Dynamics 365 / Dataverse.

Normally, when a record is created or updated in Dataverse, the platform automatically sets the Modified On and Modified By fields based on the date and time of the operation and the user who performs it. Maintaining an accurate timeline of a record's lifecycle is therefore critical for historical context and auditing.

### **Default restore behaviour:**

By default, Backup4Dynamics restores records with their original Created On and Created By values. However, the Modified On and Modified By values are not restored. Instead, Dataverse automatically overwrites them with the current date and time and the user performing the restore.

### **Preserving Modified On and Modified By:**

When the Preserve Backup Values feature is configured, Backup4Dynamics retains the original timestamp and user stored in your backup. This keeps your record's historical timeline and ownership trail intact.

**Example:**

Suppose a record in the backup has the following values:

<table data-header-hidden><thead><tr><th valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Field</td><td valign="top">Backup Value</td></tr><tr><td valign="top">Record Name</td><td valign="top">A. Datum Corporation</td></tr><tr><td valign="top">Created On</td><td valign="top">January 10, 2025 10:00 AM</td></tr><tr><td valign="top">Modified On</td><td valign="top">March 15, 2025 02:30 PM</td></tr><tr><td valign="top">Modified By</td><td valign="top">John Smith</td></tr></tbody></table>

If this record is restored on September 29, 2026:

* **Default behaviour:** Created On is restored as January 10, 2025 10:00 AM. Modified On is set to the restore date and time, and Modified By is set to the user who performed the restore.
* **With Preserve Backup Values configured:** Created On remains January 10, 2025 10:00 AM, Modified On is restored as March 15, 2025 02:30 PM, and Modified By is restored as John Smith.

This is useful when you need to maintain the original record history and timelines.

### **How to configure:**

Backup4Dynamics uses a plugin to preserve the value from the backup during the record creation or update operation.

The plugin intercepts the relevant Dataverse operation and applies the backup values for the Modified On and Modified By fields.

#### **Prerequisites**&#x20;

Before configuring this feature, ensure that:

* Backup4Dynamics is installed in the Dataverse environment.
* You have sufficient Dataverse privileges to manage plugin steps.
* You have access to the Power Platform admin center or the appropriate Dataverse administration tools, i.e., Plugin Registration Tool, XRM Toolbox.

#### **Preserve Modified On and Modified By for Email, Phone Call, Task, Appointment:**

Backup4Dynamics provides pre-registered plugin steps for the following activity entities:

* Email
* Phone Call
* Task
* Appointment
* Notes

These plugin steps are available within the Backup4Dynamics CRM solution but are disabled by default.

To preserve the “Modified On” and “Modified By” for any of these entities need to enable the plugin steps. Below are the detailed steps:&#x20;

**Step 1: Open the Power Apps Maker Portal**

Open the Power Apps environment containing your Backup4Dynamics installation.

Navigate to:

**Solutions → Backup4Dynamics → Objects → Plug-in steps**

<figure><img src="https://272130504-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M0QoyqUVI8_HaZ9FOSL%2Fuploads%2FGQQGWWYZdXGCJ7a7H0L4%2Fimage.png?alt=media&amp;token=cb85e6b1-8e67-4a46-9cf5-2df300922127" alt=""><figcaption></figcaption></figure>

The pre-registered steps are available for:

* Email
* Phone Call
* Task
* Appointment
* Notes

**Step 2: Enable the Required Plugin Step**

Enable the plugin step for the required activity.

Only enable the steps for the entities where Modified On and Modified By preservation is required.

For example, if you want to preserve Modified On and Modified By only for Email records, enable the Email plugin step and leave the other activity plugin steps disabled.

<figure><img src="https://272130504-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M0QoyqUVI8_HaZ9FOSL%2Fuploads%2FwxxSSCD0CFHEv2Jd8Qau%2Fimage.png?alt=media&amp;token=aa70f665-bb12-4320-8e44-3b53a6d65ddd" alt=""><figcaption></figcaption></figure>

#### **Preserve Modified On and Modified By for Other Entities**

For entities other than the pre-configured activities, Backup4Dynamics does not provide pre-registered plugin steps.

If you want to preserve the Modified On and Modified By values for another entity, i.e., account, contact, lead, etc., you must manually register the Backup4Dynamics plugin assembly for that entity. Kindly follow the steps below –

**Step 1: Open Plugin Registration or XrmToolBox**

Locate the Backup4Dynamics plugin assembly.

<figure><img src="https://272130504-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M0QoyqUVI8_HaZ9FOSL%2Fuploads%2FlVZeWQfXrVlGtUIAhKK6%2Fimage.png?alt=media&amp;token=da0c8054-942d-4493-832e-021c9d1ae725" alt=""><figcaption></figcaption></figure>

**Step 2: Select the Backup4Dynamics Plugin Assembly**

Locate the Backup4Dynamics assembly that provides the Modified On and Modified By preservation functionality.

Select the assembly and add a step for the required entity.

<figure><img src="https://272130504-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M0QoyqUVI8_HaZ9FOSL%2Fuploads%2FvD9jRQDxEsvM5sY0HOh7%2Fimage.png?alt=media&amp;token=72254bff-df74-44db-8a3d-a4e7921a8985" alt=""><figcaption></figcaption></figure>

**On Create** - A Create step is required when you want to preserve the Modified On and Modified By values when a deleted record is created.

<figure><img src="https://272130504-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M0QoyqUVI8_HaZ9FOSL%2Fuploads%2F4YrNg3UZwzPlJ3QaG91o%2Fimage.png?alt=media&amp;token=5c592439-8373-47f1-bc61-33bdca687bc9" alt=""><figcaption></figcaption></figure>

**On Update** - An Update step is required when you want to preserve the Modified On and Modified By values when an existing record is updated.

<figure><img src="https://272130504-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M0QoyqUVI8_HaZ9FOSL%2Fuploads%2Frhvt3rYiKkfJXSJ8FAHk%2Fimage.png?alt=media&amp;token=12917964-93a8-446b-9ca0-27c23812ffd1" alt=""><figcaption></figcaption></figure>

**Note** – The Preserve Modified On and Modified By feature does not work when the Bypass Automation option is enabled during restore.
