Sage 100

4.50.3 - Import into GL General Journal Entry with an 11 character GL Account...the import works fine on my side with their data and I don't need to make any changes at all to the masking of the Account Key, but once I get it over to the client side, it fails. I have tried changing the Length of the field from 9 to 11 (which does not stick and changes right back to 9), assigning the Account Key from a temp field, everything we normally do to get it to work. Other than DSD Multi-Currency possibly being an issue with somehow changing the DD's , does anyone else have any thoughts on a workaround to bring in a longer account number or encountered this in the 4.50 version?

The account key would be 9 characters -- are you sure you are importing on your side to the account key and not the full GL? Apologies if you exported and imported the definition to the customer site -- but the second part of your explanation about the account key going back to 9 sounds right since I believe the key is only 9 characters.

I don't have an answer for this, but I'll tell you I'm sure tired of VI crap working one place and not working another with the same version. Or what Harold and I just had - I created a new import and that was the only thing installed on the client's site and suddenly an old import stopped working. And it didn't work on my machine or his, either. But it had been working up until the new one was imported. There has got to be a ton of weird crap going on behind the scenes in VI - like linked to the C++ install or something. Over it tonight.

For many versions now, I've been either able to change the length of the Account Key field and have it read the full GL Account from the source file OR assign the Account Key to a temp field rather than replace, but for some reason, it's just not working for the client to replace the full account from the import file. Beth - my co-workers and I were just complaining about the same thing today about how inconsistent the module is.

Sounds like you're using VI, have you considered GL Exchange?

@AmberStoneburg Interesting that you have been able to change the account key in the past and have it worked. I always import the account # to a temp field and then calc the account key from the temp field. That method has worked like a champ for many years now. @BethBowers Does the import still fail after recreating it on the client side? My PR VI dies EVERY time I install anything (PU, TTU, or IRD). I have to remove one field (hrs recpt amount) and reinsert it. Then it starts working. I also have problems with PR UDF's after installing updates. Rebuilding UDF's should probably be standard procedure but when clients have a LOT of them in different tables, this becomes a royal PITA.

@JeffSchwenk - the import (and a prior version of the import) creates sales orders. The import had never imported the unit price - instead, it had imported the Qty Ordered and calculated the extension based on an imported temp field and the VI job would calc the Unit Price. This was 2 versions of the import, working on 4.4 for like a year now. Client is still on 4.4. So, the extension stopped calculating because the Qty Ordered was no longer bringing in the qty it had imported, even though that field was prior to the extension field and you can clearly see it IS importing a qty. I had to import the Qty into a temp field and calc that way. AND the unit price stopped calculating and I had to add a line to calc the Unit Price. And all of this happened on all 3 machines using an import that had been working, based on a prior version that had been working. Some of the stuff in VI HAS to be dependent on the OS, not MAS. Nothing else makes sense.

Not quite ready to blame this entirely (and only) on Sage. We encounter the same issues occasionally when creating Access db's for clients. The macro/script/query works great on our workstations with client data but when we put the DB on their workstation, the logic blows up. Mud on our face and more time spent trying figure out what is different on the client's WS.

you should be able to change the length of the field. check the Source Substring checkbox. Start Pos = 1 Length = 9 Max = (their maximum GL length) i just did one with the max = 18. it works fine. We import their full account number with dashes. No temp fields required. debits and credits can be in separate columns or you can have one column with the amount and it will treat negatives as credits and positives as debits. Just use the debit field.