Support for personal views, not only system views
Support for personal views, not only system views when setting the filter for the retention.
Only relevant views
Filter out some of the non-relevant system views from the filtering list:
- Advanced find view
- Quick Find view
- Lookup view
- Associated view
Enable use of FetchXML directly as a filter
Add support for "advanced filter" where one can upload a FetchXML directly which is then validated.
Simulation/test feature
Set up a "preliminary filter" which will show examples and quantities of which records will be affected. Then when everything is approved, it will be put into effect.
Azure Datalake synchronization
Have the capabilities of synchronizing the archived data to a datalake OR "Bring-your-own-datalake" logic with a good datastructure that is easy to use from example Azure Synapse Analytics/Data Flows etc.
Replicate Security Model
Replicate Security Model in dataverse in all aspects, including all sharings (full POA), hierarchical security etc.
Error log
Surface error log in case something has gone wrong. Preferably in line with the new KQL methods of Azure log analytics.
Restore data
Capability of being able to restore data from Long Term storage. Will probably be a common scenario when someone has set a filter that is too generous and hence need to restore some records. Intermediary method for this would be to have an instruction of how this can be done using API:s and le...
AI driven suggestions on data that could be archived
Utilize AI methods to recommend datastructures in dataverse that are never used and hence could be archived.
Data source dependency clarification
If a datasource needs to be removed, there should be the possibility to see all downstream dependencies, in for instance a tabulated list or even better a graphical view. From this each components should be clickable easily manage and remove the dependency.