Applies to Product - Dynamics 365 Commerce
What’s happening?
The batch job for archiving credit card transaction data is not deleting the data as expected, resulting in no reduction in table size.
Reason:
This may be related to the size of the database and the number of transactions being processed. It has been noted that when there is a large amount of data, the job may fail to delete it properly.
Resolution:
- Ensure that the batch job "Archive credit card transaction" is configured correctly.
- Set the "Minimum transaction age" field to a value that reflects the oldest transaction date available (e.g., 300 to 200 days).
- Execute the batch job and then run it again with a reduced value (e.g., from 200 days to 150 days).
- Perform a second execution of the batch job for 100 days and validate if the information has been deleted and if the size of the tables has decreased.