![]() Long term data retention and existing delete action and pluginsĪll the existing delete action cascade relationships and plugins for tables are executed when a data retention policy is run on the table. When a maker enables retention on a parent root table, it also enables retention for all child tables. The data is always secured with Dataverse security backed by Azure Active Directory.Ĭurrently, audit, elastic tables, and images aren't supported for long term retention.Īdmins set retention policies on tables when the application maker has enabled long term retention for the table. The retained data is never moved out of Dataverse, it's stored in a Dataverse managed data lake. Avoid IT investments required to build and maintain custom solutions for long term retention of historical application data.Īpplication admins set up custom policies for a table with criterion to retain data long term.Access the read-only data for limited inquiry purposes.Securely retain the historical application data long term for audit, legal, and regulatory requirements.It allows organizations to get immediate and ongoing benefits: Data lifecycle is completed.ĭataverse delivers native platform support for long term retention of data. Retained for compliance, audit, and legal discovery. Also referred to as live data.ĭata is immutable and read-only. Accessed across all application workflows. First active data, which over time transitions to inactive data, and finally transitions to deleted data.ĭata is readily available and transformed via apps. ![]() Consider the business application data lifecycle in three stages.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |