Sage 100

What's the secret to getting a GL Journal import to work using the ""Raw Account"" instead of the Account Key? I thought it was supposed to convert it and it does, if the account is 9 characters or less. The import I am trying has a 10 character account number and the conversion is just dropping the last segment. Any ideas? I don't want to have to edit all my import files to get the Account Key in there.

Are you using VI or GL exchange? Either way I thought it converts automatically.

I am interested in this as well because I just had a customer where I could swear that there had been some change with how VI handled these account numbers.

You can change the source substring length to 10 and that should bring in the full account.

@CatherineFrias is jogging my memory - that's exactly what made it work.

Trying to use VI so I don't need all the other info in the file necessary for GL Exchange. I thought it converted it as well, but the Account Key is 9 characters and it dumps the last segment on my 10 character account.

@CatherineFrias - I'll give that a shot

That was the fix. Too simple... Thanks @CatherineFrias

I import the full account number into a temp field, then link the GL account to the temp field. Has worked for me for the past four years.

This is also used (expanding the source substring) when importing in item extended descriptions into the ItemCodeDesc field. Same concept.

thanks @JeffSchwenk - I am running a standard GL journal import after an upgrade to 4.5 and it was dropping the GL account after 9 characters (which it didn't do on 4.2). The temp field takes care of that - but now my import job takes 30 minutes rather than 30 seconds like it took in version 4.2. Thanks for the upgrade Sage!

How many lines are in play? I migrated a Peachtree install to MAS v4.4 and imported two years of GL history. Each month had between 1200 - 1500 lines. Total import time for that was less than three minutes........

about 1500 lines, I've tried switching to header/line separate and that doesn't seem to help. I'll try switching to ""on host"" and see if that makes a difference. Wasn't checked in the 4.2 version, but the actual file is on the host - maybe it's having to go around in a circle reading the data.

Did you migrate the import also? If so, try rewriting it from scratch. Might make a difference. VI is peculiar is many ways. I don't like to set the ""on host:"" because you may miss an error message. Send me a print out if that would help.

I rewrote it because we switched from Sage extended solution Multi-Company to DSD Multi-Company. I'll try a few other things and if it still drags I'll shoot you a print out. It could be something to do with DSD enhancement slowing it down - who knows....

Good point on the DSD enhancement. Can you export the import to a vanilla install for testing?

Yes, when you add GLMU it really slow down the VI imports. I was told it was due to all the features added when they merged the multi-company extended solution into the DSD multi-company. I will discuss it with our programmng team to see what can be done.

I am working with our programming team for a fix for slow vi imports on system with DSD's Multi-company (v4.4 or v4.5)

if you get this fixed, can you assist Alnoor with the slow AR customer renumbering???

@JimWoodhead - I'm looking for the GL VI import file that fixes the import speed issue. I found the APMU file but not the GL one. Did you get one from development, and if so can you shoot it over to me?

Check private messages