Sage 100

Today is a fun day. Another client who is on 4.3. Did an item merge a couple of weeks ago. It was all forked up, possibly due to old leftover Hightower junk. (I just wrote the imports, didn't run it, but still - you can't screw it up.) ANYWAY, what ended up was the items were merged in CI_Item but were NOT merged in IM1. So now it gets better. The IM1 Ext Desc flag is turned on. The Ext Desc Key field is blank in CI_Item. You can't import directly into CI_Item in 4.3, so even though we have a pre-merge file, it doesn't appear to do us any good. Any hope at all????????

Can you restore the xxxci and xxxim folders from ""a couple of weeks ago"" prior to the merge? You could add them to a generic install on your laptop, perform the merge and then just copy the CI_Item table back to the live installation.

That would almost work except in PO they IM1 records are still out there, but I guess they could get around that. Good thought - I'll see what that would entail.

Oh, wait - new items added since then. BUMMER.

Darn... Looks like an RCF.

LOL - tell me what you really think.

Several years ago I had a similar probelm during a 4.3 upgrade. After exhausting all my attempts to fix i called Sage support who had a way to populate the extended description files. I searched my files for any old documentation or case # but apparantly i didn't take time to document the fix. The good news is it can be fixed.

@HaroldWestover - how interesting. I would never think to call Sage for help like this - live and learn!