Long story short, I ran a mass update in SQL on the Item table in RMS Store Ops 2.0. I updated about 26000 items. Now when I try to run the Data Upload worksheet (401) in Headquarters, the HQ client churns aways for about a half-hour, then times out.
Is there any way to "short-circuit" the item upload in HQ? I tried manually setting the ItemDynamic.SnapShotTime field to a later date, hoping that it would trick HQ into thinking these items were updated already, but no luck. I don't quite know how RMS determines something in StoreOps needs to be uploaded to HQ; is there a table in StoreOps that controls that (I looked, and couldn't find anything with an obvious name).
Restoring the StoreOps backup to the pre-update state is not an option; we've been ringing up sales all day Fortunatley, my sales transactions are uploading (In the upload process, transactions upload before items), so at least I have some sales figures in HQ, but I have to manually run the worksheet, then wait a half-hour for it to time out.