QUOTE (SteveTNT @ Aug 2 2010, 09:28 PM)

I will be going live in a few weeks and am reading about a lot of problems with Webconnect. It seems like a lot of folks are spending a lot of time trying to fix problems.
My question is whether I'd be better off skipping Webconnect and downloading orders from NS and importing into Quickbooks? Or, does export/import have the same problems. I understand that export/import is a manual operation, but if it really works that might save time over "fixing" Webconnect errors.
I don't think you'll be able to import orders via import, just customers, items, vendors. Unless I'm missing something. Is there another alternative to using WebConnect for order import?
QUOTE (SteveTNT @ Aug 2 2010, 09:28 PM)

Related problem. Export/import might give me a chance to fix the QB limitation of a 31 character Name field. I'm not sure yet of the details of how I'll work around this, but I could alter the NS export - maybe cut and paste to exchange Name and Part Number (letting part number be the QB "Name") before the QB import. As long as I maintain Mfg part numbers in QB I should be able to generate POs.
When you import products using Excel instead of syncing with WebConnect, do they subsequently link up when you bring in orders with WebConnect? Maybe this is a way around my variations problem.
Sorry I'm not adding information but asking more questions. Please let us know what you try and what works and what doesn't.
Hilary
www.sundialwire.com