Power Dynamics
  • Power Dynamics
  • 🍕My name
  • D365 CE
    • Copilot
      • 🥐Add Copilot into Rich Text Control
    • Sales
      • Copilot in D365 Sales
      • Export record to PDF
    • Customer Experience
      • Omnichannel
        • 🐚Internal Live Chat in MDA
        • 📢Add Chat Widget to Power Pages - Proactive Chat
      • Attachment Control
      • Case Routing: Basic Routing rule set
      • Custom SLA for any Entity
    • Field Service
  • Power Platform
    • Dataverse
      • Use case for the feature of Record ownership across Business Unit
      • 💡Workaround: Change the OOB "Exchange Rate" of a record
      • Using a Virtual Entity to store historical log (sample)
      • Disable Empty Address record
      • Using Adaptive card
      • Block Unmanaged Customizations
      • 🪃Recycle Bin on Dataverse (Preview)
    • Model Driven App
      • 💡Run SSRS report on MDA mobile
      • 💡Tip: Create a Security Role with "App Opener" minimum privileges
      • Tag @person to notify in MDA
      • Auto search on the Lookup field
      • Activities with multiple related records
      • Embedded Power BI - Dashboard
      • Embedded Power BI - Form
      • "Custom Help" - Is it help?
      • New modern Command Bar
      • Tip: Hide the button "Add Existing Record" on subgrid
      • Custom Page - Why not?
      • Hiding sensitive column data
    • Canvas App
    • Fabric & Power BI
      • New Text slicer
      • Dataverse link to Microsoft Fabric
      • 💡Leveraging Interactive Warehouse Floor Maps in Power BI
      • Calculation Group for Time Intelligence
    • Power Automate
      • ✅Sequential Approval
      • 📤Create an Appointment by Outlook Graph API
      • Dowload SSRS Report and Send email
      • Power Automate: Add a table in Email
      • 💡Tips: Get "DisplayName" of the Lookup field on Power Automate
      • E-sign: Power Automate & DocuSign
  • D365 Finance & Operation
    • General
      • 🇻🇳D365 FnO - Virtual entities: Use case
    • Finance
      • Consolidating Customer & Vendor Balances
    • Supply Chain
      • Landed Cost Series
        • Landed Cost- Essential Configuration
        • Landed Cost Scenarios 1
Powered by GitBook
On this page
  • Recovering Deleted Data in Microsoft Dataverse
  • Enabling the "Recycle Bin" for an environment
  • How to restore deleted records?
  • Testing now...

Was this helpful?

🪃Recycle Bin on Dataverse (Preview)

#PowerPlatform, #Dataverse, #Restore, #RecycleBin

PreviousBlock Unmanaged CustomizationsNextModel Driven App

Last updated 6 months ago

Recovering Deleted Data in Microsoft Dataverse

In Microsoft Dataverse, records or transactions can be deleted through various means - manually by users, automatically by system processes, or through bulk deletion actions. These deletions can occur intentionally or accidentally

The challenge lies in the recovery of deleted data. Historically, restoring records in Dataverse could be difficult, with some data potentially being permanently lost. To mitigate this issue, Microsoft provides a solution: the Recycle bin.

The Recycle bin in Microsoft Dataverse is designed to recover table record data regardless of how it was deleted—covering all deletion scenarios. This feature operates within a flexible, configurable timeframe, ensuring that users have a window in which they can retrieve their lost data.

Okay.. now.. let's try this preview feature with me!

Enabling the "Recycle Bin" for an environment

In the Power Platform Admin Center > Setting > under the Feature setting: Enable Recycle bin for Dataverse table and specify the Time interval as below.

Next, wait at least 10 minutes for the configuration process to complete.

How to restore deleted records?

Restore deleted records:

To restore deleted records, you go back to the Power Platform Admin Center > Select the environment and click Setting. After that, under Data Management > click "View Deleted Record (Preview).

The system will show all deleted records and you can select one or multiple records that need to be restored. After that, click the button Restore to recall data.

and then, checking the record after restoring.

Testing now...

I will test my environment (without D365 Applications). I will separate the test case for data checking after restoring deleted records.

For instance, I will check on 2 entities:

  • Parent entity: Account

  • Child entity: Deal

  • The relationship: Account (1:n) Deal

Test Case 1: Delete the child entity "Deal" with the lookup field "Account" containing data.

Expectation after restoring deleted Deal record: The Account field will be restored with the original data

Before deleting: Deal record - the Account field contains value "NTD Asia Corp"

After Restoring: The testing passed. The Deal record has been restored successfully with the original Account field value.

Test Case 2: Delete the parent entity "Account" associated with the Deal records.

I have 2 Deal records associated with the Account "Hoang Quan Corp." -> After deleting the Account "Hoang Quan Corp.", this value has been removed from 2 related Deal records before.

Now, after restoring the Account "Hoang Quan Corp.", I hope that this value will be associated with Deal records before.

After restoring: The Account "Hoang Quan Corp." has been restored and associated with 2 Deal records before. -> The testing passed.

Thank you for reading & Hoping well! [NTD]yns.asia

🎉
👍
Page cover image
Enabling the Recycle bin for Dataverse tables
View Deleted Record (Preview)
Restoring selected record