web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Service | Customer Service, Contact Center, Fie...
Suggested Answer

Unable to Save "Enable Long-Term Retention" Setting on Table Recording (msdyn_ocrecording)

(0) ShareShare
ReportReport
Posted on by 36

Hi everyone,

I'm trying to enable Long-Term Retention for the Microsoft standard Dataverse table msdyn_ocrecording (Recording table used by Omnichannel/Customer Service).

I'm following the Microsoft documentation:
Enable a table for long-term retention

Environment details:


  • Dataverse environment is a Managed Environment

  • I have the required administrator permissions

  • The table is a Microsoft standard table (msdyn_ocrecording)

  • I open the table properties and select the Enable long-term retention checkbox

  •  

Issue:
After selecting the checkbox, the Save button remains disabled, so I cannot save the change. No validation or error message is displayed.

I'm trying to determine:


  1. Is msdyn_ocrecording supported for Dataverse Long-Term Retention?

  2. Are there any restrictions on enabling retention for Microsoft-managed/solution-managed tables?

  3. Has anyone successfully enabled Long-Term Retention on this table or similar Omnichannel recording tables?

  4.  

Any guidance would be appreciated.

Screenshot 2026-06-30 095716.png
I have the same question (0)
  • Suggested answer
    Manoj - ManoVerse Profile Picture
    1,396 Super User 2026 Season 1 on at

    This table is not customizable and it also doesn’t have a parent (cascade) relationship with any other table, so you won’t be able to enable long-term retention on it. In Dataverse, retention can be enabled either directly on a supported table or through a parent table so that it flows to child tables. In this case, msdyn_ocrecording does not fit into either option.
    Also, this table mainly stores recording-related details like links to audio/video files, timestamps, and conversation references , actual recording files are stored outside Dataverse (usually in Azure). Because of this, it is not a core business table, and typically it doesn’t drive significant Dataverse database growth. So, in most cases, long-term retention is not really required for this table.

  • Suggested answer
    11manish Profile Picture
    1,125 on at
    First, verify that Long-Term Retention can be enabled on a custom Dataverse table in the same environment. If that works but msdyn_ocrecording still cannot be saved, it's very likely that the table does not support customer-enabled Long-Term Retention due to being a Microsoft-managed system table.

    If you need a definitive answer, I recommend opening a Microsoft Support ticket. They can confirm whether msdyn_ocrecording is supported for Long-Term Retention or whether this is a product limitation. If it's intended to be supported, Support can also investigate why the Save button remains disabled despite meeting the documented prerequisites.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Season of Sharing Community Challenge Winners!

Congratulations to our community stars!

Women in Power Builds Momentum

Expanding mentorship, skilling, and AI innovation

Congratulations to the June Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Service | Customer Service, Contact Center, Field Service, Guides

#1
11manish Profile Picture

11manish 27

#2
KristineRisberg Profile Picture

KristineRisberg 19

#3
Manoj - ManoVerse Profile Picture

Manoj - ManoVerse 17 Super User 2026 Season 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans