8

Current Issue Facing

Customers who need to clear or reset large volumes of business data in a Dataverse environment are currently required to re‑create or re‑implement all customizations when using supported approaches (e.g., environment re‑creation or schema‑only copy). This creates significant overhead, especially for mature environments with extensive customizations.


There is currently no supported option that allows customers to:

  • Fully remove business data
  • Retain existing customizations and configurations
  • Remain within a supported Microsoft configuration


Customer Impact

Currently, re‑implementing all customizations is:

  • Extremely time‑consuming
  • Resource‑intensive
  • Risky for production‑grade environments with complex solutions


This becomes especially challenging for customers with:

  1. Large numbers of entities, forms, views, flows, plugins, and integrations
  2. Long‑running environments that have evolved over time
  3. Limited windows for downtime or rework


As a result, customers may delay necessary cleanup activities or operate in sub‑optimal states due to the lack of a supported alternative.


Proposed Approach

Introduce a supported mechanism or tooling that allows customers to:

  • Reset or remove business data in a Dataverse environment
  • Preserve customizations (schema, solutions, configurations)
  • Avoid full environment re‑creation and re‑implementation


This could be delivered as:

  • A controlled platform capability
  • An administrative operation with safeguards
  • A documented, supported workflow for specific scenarios


Providing such a capability would:

  • Reduce operational burden for customers
  • Lower risk during environment lifecycle management
  • Improve overall customer experience for enterprise and long‑term Dataverse users
Category: Dataverse
STATUS DETAILS
New

Comments

B

Totally agree!! This is a practical approach for customers throughout the entire system lifecycle, from implementation to ongoing maintenance.

Category: Dataverse