You’re offline. This is a read only version of the page.
63
A sales associate noticed an item we've had since 2017 would not ring up at POS, and I followed the rabbit hole and discovered somehow the item no longer existed in Store Operations Manager for that store (it is still in the system of our other location). The item and all of its sales data is still in HQ Manager, but we had to resort to a new Item Download worksheet to get the item back into the local to be sold.
The item is gone from all previous purchase orders, transfers, sales, etc.
Is there any way to import the sales/movement data from HQ to that store's local system, or are we doomed to have inconsistent data?
We had a system crash over the weekend, and I do still have a database backup from November 25th, as I'd forgotten to perform the backup this past Monday (Dec 2nd).
Would that possibly restore sales data?
UPDATE: There are more items being discovered that have gone missing from the local system, but creating an Item Update worksheet with the items in question only fixes their item entry; the sales, movement, and purchase data are still missing from local. I am tempted to use the backup file, but I don't know if this will restore the data in the way that I need it to.
Thanks,
Your friendly neighborhood Pawlybeans, aka Paul H
Hi Paul,
There is not a way to import the info; but there are a couple options to resolve this issue.
1. You could Export the store from HQ (at a time when nothing is being done at the store and after a 401 has uploaded all data from the store to HQ); and then restore this exported backup at the store. This should then contain all sales data, etc. for the store.
NOTE: If you do this I would make a backup of the existing store database, shut down HQ Client at the store and HQ Server at HQ, then delete the store database and restore the exported backup from HQ as the same DB name. Depending on DB size, location, etc. you may want to test this first to see how long it takes to export the DB, get a copy of the backup file to the store and restore (in testing use a different DB name).
2. If you want to try fixing the data in the existing store database, please create a support ticket and an engineer should be able to determine the necessary SQL scripts to fix the issue.
I would NOT restore the backup from 11/25 (or in reality any older backup at the store level when using HQ) as this can cause issues since sales, purchase orders, transfers, etc. may already be in HQ from the time after the backup was made.
I'm not sure if it will help, but the below query can be used to see the items that have been deleted through the UI:
NOTE: The RecordID is the ID from the item table for the item; and is not the Item Lookup Code. But the date may help if a number of items were removed and workers are able to recall what was done at that time.
select * from recorddeletedlog where tablename = 'Item'
Hopefully this helps.
Todd
Share
Report
All responses (
Answers (
