Quick Summary: The app expects new ERP data at least every 24 hours. If the import date becomes older than 24 hours, it will turn red and may also display an import error. Use the steps below to verify status, validate the control file, update the extraction date, and reprocess where required.
When the Import Date Turns Red
The app expects to receive data from the ERP at least once every 24 hours.
If the import date is older than 24 hours, the timestamp displayed in the top left navigation area will turn red. This indicates that the app is more than 24 hours behind ERP data.
The app may also show an error message indicating that something is wrong with the data import.
Correcting the Date
Step 1: Check the Import Status
First, check the status of the import within the app.
If you can log in successfully and no error is displayed, the import is likely in the queue.In this case the status will show as Queued.
Large sales days or high transaction volume can increase import duration.
This behaviour is normal and the import should complete without intervention.
Once the refresh begins, the app will log all users out and display a message that an update is running.
Step 2: Understand the Control File
The date and time displayed on the app dashboard come from the control file, which is imported daily.
This file:
Resides on the client server
Sits in the
to_netstockfolder until the app picks it up and imports it
Step 3: Validate and Correct the Extraction Date
If the control file is generated manually and a user with sufficient permissions can access the to_netstock folder:
Open the control file.
Check that the extraction date recorded in the file is correct.
If the date is incorrect, update the extraction date in the control file.
Reprocess the data using the standard refresh process.
It is recommended to generate a new control file from the ERP so that the information in the file matches the ERP data as closely as possible.
Step 4: When the Date Still Does Not Move Forward (Optional)
If the corrected extraction date in the control file is the same as, or older than, the date already shown in the app, the import automatically fails. The app always expects a control file with a more recent date.
In that case, contact a support consultant for assistance.
If the Netstock data extraction process generates the control file automatically rather than manually, the support team needs to investigate what went wrong with generation or transfer.
Correcting an Error
If a user logs in and an import error message appears, then something has interrupted the import process.
Click the information icon next to the error to view detail. The message may indicate a missing file or a file that failed during import.
Once the issue is corrected, reprocess the data.
If the error appears again, log the issue with Support.
Forget about these 👇 😞 😐 😃 Have your say here!