Set Next Transaction Number

(0) Share

Report

Posted on by Mary Scheible

580

The register database crashed and we had to restore from a backup. Unfortunately, that backup was a couple weeks old. Fortunately, that data was up in HQ, at least. Initially, we saw old transactions being replaced in HQ, because of duplicate transaction numbers. So we used the function in Store Ops Administrator to "set next transaction number" out a few hundred. We thought everything was okay, because I was just checking the Transaction record in HQ (still there, all good). Well the TransactionEntry records are being erased/replaced in HQ, because the TransactionEntry.ID value is the same. Since it is an identity field I cannot manually (via SQL) increase the last one. Why would they allow you to increase the TransactionNumber and then the ID field causes problems? How do we fix this?

thanks,

Mary

*This post is locked for comments

All responses (3)

Answers (0)

Community Member Microsoft Employee on at

Like (0)

Report

RE: Set Next Transaction Number

You may want to consider creating a service request at MS as that database may require being rebuilt now. Under those types of situations Mary, you would want to export a new copy of the stores database from HQ (as it is recent) vs. restoring one locally that was two weeks old. The information now being reported to HQ is now corrupting that one I suspect.
raelhefn on at

Like (0)

Report

RE: Set Next Transaction Number

I think the solution for your issue is starting from restore last backup for your HQ database after that export your store database from hq administrator, after that restore in store database at your store register, set your next transaction number.

this issue not occurred from setting your next transaction number this done because your restored store database not synchronized with HQ so duplications occurred in transaction details level.
Suggested answer

Mary Scheible 580 on at

Like (0)

Report

RE: Set Next Transaction Number

I did a reseed statement in SQL to up the TransactionEntry.ID.

DBCC CHECKIDENT (yourtable, reseed, xxxxx)

That stopped the deletions. Not sure if I can recover the data that was overwritten in HQ from an HQ backup we have or not.

Mary