Quick Summary: Run a Full Refresh to trigger a complete overnight-style data update from your ERP, or run Reprocess Data to reapply configuration changes using already synced files. Both options are accessed from the System, Data refresh screen.
Before You Start: Refreshes Can Cause Downtime
Full Refresh and Reprocess Data can make the app temporarily unavailable. Once processing begins, users are logged out and cannot access the app until the update completes.
The duration varies depending on factors such as data volume, integration method, database load, and processing demand. In some environments, this can take several hours.
Do not use Full Refresh or Reprocess Data as a routine first step in troubleshooting. If either action is required, make sure users understand the potential downtime and choose an appropriate time to run it.
When to Refresh
In most environments, it is not necessary to refresh more than once per day, and in some cases the size of your data or the integration method makes frequent refreshes impractical.
Use an additional refresh when:
You have made configuration or policy changes that must be applied to live data
There is a specific need to bring ERP changes into the app sooner than the next scheduled extraction
You have resolved a data file error and need to reprocess the import
Step 1: Go to Data refresh
In the app, navigate to System > Data refresh in the left pane.
Step 2: Choose Full Refresh or Reprocess Data
On the Data refresh screen, you will see two primary actions.
Full Refresh
Initiates the full overnight process
Extracts data from your ERP, syncs it to the cloud servers, and processes it into your instance of the app
You can continue to use the app while data is being received from your ERP
Once the import begins processing, the app will lock users out until the update completes
Reprocess Data
Used after changes to configuration or other settings so that these changes are applied to the existing data set
Does not pull new files from your ERP
Reruns processing on the cloud servers using data that was already synced previously
Step 3: Optional Refresh Settings
The following options are available on the Data refresh screen and affect how the batch runs.
Regenerate forecasts
Forecasts are recalculated during the refresh, but frozen forecasts remain unchanged. Disable this option if you want to shorten the refresh duration.
Skip Pivot update
Visible when Pivot forecasting is enabled. Pivot is not updated, but forecasts are still synced into the app. Enable this option to reduce refresh duration.
Skip MD5 validation
Skips the file validation check at the start of the batch. This should be used with caution and only when there is a specific reason to bypass validation.
If Pivot forecasting and Import Forecasts are both enabled, the option to regenerate forecasts is intentionally not available. This preserves the Pivot forecast history so that:
You can see the actual forecasts that were used historically
Forecast risk and offset calculations, and therefore safety stock, are more accurate
Inventory data in the app stays aligned with Pivot forecast information
Important Behavior During Refresh
Once processing begins, the app logs users out and displays a message that the update is in progress.
Do not start another Full Refresh or Reprocess Data while an existing request is queued or processing.
Forget about these 👇 😞 😐 😃 Have your say here!