---
title: "Configure Data Caching in Warehouse Insight"
app: "Warehouse Insight"
section: "Set up"
last_updated: "2025-07-07"
url: "https://insight-works.com/kb/warehouse-insight/configure-data-caching-in-warehouse-insight/"
---

# Configure Data Caching in Warehouse Insight

Note: For optimal performance, ensure the device cache is enabled for all devices.

The Device Cache option’s main purpose is to prevent making calls to Business Central when scanning an item or bin barcode. Two additional caching options improve application loading performance (see the _Frequency options_ and _Fetch Size field_ sections). Without caching, each scan results in a call to Business Central to decode the item or bin and return the relevant data (e.g., to execute the barcode rules on the barcode and retrieve the item information). With caching on, these actions are handled on the device, without a web services call to Business Central, significantly improving performance.

To configure device caching:

1. Navigate to _Warehouse Insight Device Configurations_ in Business Central.
2. Select the required configuration card.
3. Select **Related** / **Cache Settings**and set _Cache Data_ to Yes (auto generates the default cache options).
4. Select **Cache Settings** and modify the caching options as needed (Optional):

   - Items: Used when decoding an item, lot, or serial number barcode scan.
   - Item Cross References: Used when decoding an item, lot, or serial number barcode scan.
   - Item References: Used when decoding an item, lot, or serial number barcode scan.
   - Item Identifiers: Used when decoding an item, lot, or serial number barcode scan.
   - Item Ledger Entries: Used when decoding an item, lot, or serial number barcode scan.
   - Item Units of Measure: Used when decoding an item, lot, or serial number barcode scan.
   - Barcode Rules: Used when decoding an item, lot, or serial number barcode scan.
   - Bins: Used when a bin is scanned.
   - Applications: Refers to Warehouse Insight Applications and allows the device to store copies of each applications locally to avoid re-fetching the application from Business Central each time it is opened.
   - Item Pictures: Refers to the picture associated with an item, and make image FactBoxes and image display on scanning much faster.

1. Set the frequency of each option as needed (see _Frequency options_below).
2. Set the _Fetch Size_ field (the default for most entries is 3000 records; see _Fetch Size field_ below for more information).
3. View the cache entries:

   1. Select **Configure** / **Data**  and enable **Show Cache Details Menu** (you can view the cache entries from the main menu page using **Cache Details**).
4. Delete the cache entries as needed (entire cache or specific tables).

Any new or modified records in Business Central are added to the device cache based on the configuration specified. For example, if Item Ledger Entries are added or modified, the corresponding cache on the device is updated based on the configured frequency; whereas Item changes might only be reflected once the application is restarted since the Item entry is typically set to “On Startup”.

 Note: The cache on the device is not updated when records are deleted from Business Central. If needed, you can remove deleted records from the cache by clearing it using the _Cache Details_ screen. Note: It is good practice to delete the entire cache prior to going live so previous entries made from testing/sandbox environments do not impact production scanning.

### Frequency options

The Cache Settings options have the following frequency options:

| **Frequency** | **Description** |
| --- | --- |
| Never | The Warehouse Insight application never caches the data. Whenever the application needs this data, it makes a web services call to Business Central. |
| On Startup | The Warehouse Insight application caches the data when it is launched. At 1-minute intervals, the application continues to fetch the data in batches, defined by the Fetch Size, until completely cached. |
| Periodically | The Warehouse Insight application begins to cache the data when started, like the On Startup option, and continues to check Business Central for new data after all data is loaded. These checks occur at the interval defined in the _Interval (minutes)_ field. |

### Fetch Size field

The _Fetch Size_ field on each entry determines how many records should be loaded from Business Central and sent to the device in each web services call. The default for most entries is 3000 records. If the Item table, had 9200 entries it would take 4 calls to Business Central to fully populate the Item cache (3000 + 3000 + 3000 + 200).
