Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 18 Next »

Description

Retention policies can periodically delete outdated data

Starting from BC17 you can define and set up Retention Policies for selected tables.

See https://docs.microsoft.com/en-us/dynamics365/business-central/admin-data-retention-policies

Supported tables

In Mobile WMS we have enabled the following tables to be used with Retention Policies.

They are all disabled by default and require manual setup, but the Mobile Document Queue and Mobile Print Log are created with sample configurations.

Sample configuration

The sample configurations are not enabled automatically, but they can be processed once you enable the policy:


Earlier versions of Mobile WMS (before 5.40) contained suggested Retention Policies with Retention Policy Setup Lines. This turned out to be difficult to use due to an excessive time consumption. For performance reasons it is therefore recommended to use a simple setup with a single retention period for all records in each table.

The policies can either be processed manually from the Retention Policy window or automatically using the Job Queue.

For more information on the Job Queue: https://learn.microsoft.com/en-us/dynamics365/business-central/admin-job-queues-schedule-tasks

Recommendation

The Retention Policy feature can also be configured with "Apply to all records" = false and have different retention periods for different subsets of records.

This type of configuration can be very time consuming to process and we therefore recommend to avoid having "Apply to all records" = false.

You have completed the Basic Configuration and you can use Mobile WMS.

If needed, continue with the Additional configuration (4/4)


Overview

  • No labels