Manage Storage by Deleting Documents or Compressing Data

A central role, such as the application administrator, must regularly deal with accumulating historic documents by deleting or compressing them.

Tip

Learn more about other ways to reduce the amount of data stored in a database by reading Reducing Data Stored in Business Central Databases in our Developer and IT pro documentation.

Delete documents

In certain situations, you may need to delete invoiced purchase orders. However, you cannot delete them unless you've fully invoiced for and received the items in the purchase orders. Business Central helps your out by checking for that.

Return orders are usually deleted after they're invoiced. When you post an invoice, it's transferred to the Posted Purchase Credit Memo page. If you selected the Return Shipment on Credit Memo check box on the Purchases & Payable Setup page, the invoice is transferred to the Posted Return Shipment page. You can delete the documents using the Delete Invd Purch. Ret. Orders batch job. Before deleting, the batch job checks if the purchase return orders are fully shipped and invoiced.

Blanket purchase orders are not automatically deleted after you've processed and invoiced all the related purchase orders. Instead, you can delete them with the Delete Invoiced Blanket Purchase Orders batch job.

Invoiced service orders are usually deleted automatically after they're fully invoiced. When an invoice is posted, a corresponding entry is created and can then be viewed on the Posted Service Invoices page.

Service orders are not deleted automatically, however, if the total quantity on the order has been posted from the Service Invoice page rather than from service order itself. You may need to manually delete such invoiced orders by running the Delete Invoiced Service Orders batch job.

Compress data with date compression

You can compress data in Business Central to save space in the database—which in Business Central online can even save you money. The compression, based on dates and functions, combines several old entries into one new entry.

You can compress entries that meet all of the following conditions:

• They're from closed fiscal years.
• The Open field is set to No.
• They're at least five years old. If you want to compress data less than five years old, contact your Microsoft partner.

So, for example, vendor ledger entries from previous fiscal years can be compressed so there's only one credit and one debit entry per account per month. The amount in the new entry is the sum of all the compressed entries. The date assigned is the starting date for the compressed period, such as the first day of the month (if the entries are compressed by month). After compression, you can still see the net change for each account in the previous fiscal year.

The number of entries that result from a date compression depends on how many filters you set, which fields are combined, and which period length you choose. There is always at least one entry. When the batch job is finished, you can see the result on the Date Compr. Registers page.

You can compress the following data types using batch jobs.

• Finance entries - general ledger (G/L) entries, value added tax (VAT) entries, bank account ledger entries, G/L budget entries, customer ledger entries, and vendor ledger entries.
• Warehouse entries
• Resource entries
• Item budget entries
• Fixed asset (FA) ledger entries, FA maintenance ledger entries, and FA insurance ledger entries.

When you're defining criteria for the compression, you can keep the contents of certain fields using the options under Retain Field Contents. The available fields depend on the data you're compressing.

Note

Before you can run date compression, your analysis views must be current. Learn more in the Update an analysis view section.

After the compression, the contents of the following fields are always retained: Posting Date, Vendor No., Document Type, Currency Code, Posting Group, Amount, Remaining Amount, Original Amt. (LCY), Remaining Amt. (LCY), Amount (LCY), Purchase (LCY), Inv. Discount (LCY), Pmt. Disc. Given (LCY), and Pmt. Disc. Possible.

Posting compressed entries

Compressed entries are posted slightly differently than standard posting. This is to reduce the number of new general ledger entries created by date compression, and is especially important when you keep information such as dimensions and document numbers. Date compression creates new entries as follows:

• On the General Ledger Entries page, new entries are created for the compressed entries. The Description field contains Date Compressed so the compressed entries are easy to identify.
• On ledger pages, such as the Customer Ledger Entries page, one or more new entries are created.

The posting process creates gaps in the number series for entries on the General Ledger Entries page. Those numbers are assigned to the entries on the ledger pages only. The number range assigned to the entries is available on the G/L Register page in the From Entry No. and To Entry No. fields.

Note

After you run date compression, all accounts in the ledger are locked. That means you cannot, for example, reverse vendor or bank ledger entries for any accounts affected by the compression.

The number of entries that result from a date compression depends on how many filters you set, which fields are combined, and the length of the time period you choose. There will always be at least one entry.

Warning

Date compression deletes entries, so you should always make a backup copy of the database before you run the batch job.

To run a date compression

1. Choose the icon, enter Data Administration, then choose the related link.

2. Do one of the following:

   • To use an assisted guide to set up date compression for one or more types of data, choose Data Administration Guide.
   • To set up compression for an individual type of data, choose Data Compression, Compress Entries, then choose the data to compress.

   Note

   You can only compress data more than five years old. If you want to compress data less than five years old, contact your Microsoft partner. They need to use the OnSetMinimumNumberOfYearsToKeep event in the "Date Compression" codeunit to set the threshold.

See also

Administration

Find free e-learning modules for Business Central here