web

You’re offline. This is a read only version of the page.

News and Announcements icon

Dynamics 365 CommunityForums Microsoft Dynamics 365 | Integration, Dataverse... List of Dataverse with...

Microsoft Dynamics 365 | Integration, Dataverse...

Suggested Answer

List of Dataverse with tables that can handle physical deleted records

(4) Share

Report

Report

Posted on by SV-12091130-0

8

Hi all,

last week I noticed that the UserInfo-table handles deleted records differently.

It worked with physical deleted records, rather than logical deleted records as is the "normal" way.

Does someone have a list of tables that work the same way as the UserInfo-table, namely work with physical deleted records and not logical deleted records?

It changes my approach on how to handle the kind of records when loading them into our DataWareHouse.

Thanks in advance,

Sven

Categories:

Dynamics 365 general

I have the same question (0)

All responses Img

All responses (2)

Answers Img

Answers (0)

Suggested answer

Sahan Hasitha 2,683 on at

Like (4)

Report
Copy link

Link copied!

• Detect Delete Behavior per Table
   Check TableProperties → TableType.
   System/Internal tables → often physical delete.
   Normal business tables → soft delete.
• Track Deletes Consistently
   For soft delete tables: watch ValidTo, DataAreaId, DeleteAction, or RecId presence.
   For hard delete tables: implement Change Tracking (CT) or DMF export with Change Feed so you catch the delete before it disappears.
• Recommended Approach
   Use BYOD with Change Tracking enabled → it captures hard deletes as a “tombstone row” in your SQL DB.
   Or, if using Entity Store → note that it does not track deletes (only current snapshot).
   For critical tables like UserInfo, always use BYOD + CT for DW loads.

3 people found this reply helpful.

Was this reply helpful? Yes No
Suggested answer

DAnny3211 11,417 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi,

You're correct in observing that the `UserInfo` table behaves differently by supporting **physical deletion** rather than the more common **logical deletion** used across most Dataverse tables. This distinction is important when designing data pipelines, especially for Data Warehousing scenarios.

Unfortunately, Microsoft does not publicly provide a comprehensive list of tables that support physical deletion. The behavior can vary depending on the table's origin (standard vs. custom), its role in the system, and whether it's part of legacy AX/F&O structures or native Dataverse entities.

To identify such tables, you might consider:
- Reviewing the **table metadata** via the Dataverse Web API or SDK to check for `IsLogicalDeleteEnabled` flags.
- Using **Dataverse auditing** or **Change Tracking** to monitor deletion behavior.
- Consulting the official documentation on Dataverse table types and deletion behavior.

Please verify if this information helps guide your approach.

Thanks and best regards,
Daniele
*Note: This response was prepared with support from Copilot to ensure clarity and completeness.*

1 people found this reply helpful.

Was this reply helpful? Yes No

Join the conversation

Helpful resources

Quick Links

Leaderboard > Microsoft Dynamics 365 | Integration, Dataverse, and general topics

#1

#2

ManoVerse 58 Super User 2026 Season 1

#3

Last 30 days Overall leaderboard

Featured topics

Welcome to the Microsoft Dynamics 365 forum!

Identifying an Org as CDS or Dynamics

Get batch job history log from D365 FO to Power Automate

Gross and Net Weight of Shipments feeding back into Sales Order (from External Source)

Product updates

Dynamics 365 release plans