Accpac is generally good at being able to import transactions into it however it is
a) Generally ugly to create import files for lots of the modules, such as pricing information in I/C P/O Receipts etc
b) 90% of the time when you get an error because of a invalid field the error displayed in the Import UI is not the actual cause of the error
c) when importing lots of transactions and there are a lot of errors (clients importing G/L Budgets is a good one) it stops at each one, so you fix that error, restart move on 2 lines and get another error. Why can't it scan the file first and tell you ALL of the errors (and yes I know that you should have the file right in the first place but end users don't!)
d) The import \ export process is generally difficult and you really have to be an expert user or reseller to get it to work well. can't this process be made simpler.
e) rebuild the budget import export process, clients generally make a hash of this as you need to go and set criteria's for fiscal years, and budget sets and they just don't get it. When you export a budget can't the system prompt you for this basic stuff?
by: Kerry J. | over a year ago | General Enhancements
Comments
Yes, yes, yes!!
The import function in Accpac is horrendous.
Had it not been for a design flaw in module ICT that prevents multiple postings to the same company's GL account, I wouldn't need to use importing for much, if at all...
I've imported a few entries this month-end. These entries include recurring invoices and a recurring entry.
One went in without a problem.
One went in with the normal incorrect error message (which has no effect on the import, I just need to delete the restart record).
One has failed. This was a GL import into a single company (not ICT). The template was identical to last month's template, which succeeded. This month, Accpac couldn't get past the journal header sheet, wrongly claiming that i) there was no date; and ii) the source ledger wasn't identified.
So, once again, I've emailed the screenshot to the support desk, along with the monthly copy of the import file, and await the support desk's response.
How much time do I need to waste trying to import these things, only to find that I have to type up hundreds of rows each month, because Accpac can't import properly?
I have reviewed the import failure per my posting above.
The error message said that there was no date and that it had stopped processing at Journal_Headers.
In fact, there was a date missing in a far-right column in Journal_Details.
So the error messages are misleading.
The user would not type the missing dates in by hand; there should be no need to import them.
My next challenge was to import figures into budget set #2. So I recycled the same budget template as the (eventually) successful import for budget set #1.
Error message "Please mark all required fields."
The ususal email went to the beleagured reseller. (I feel sorry for him, really I do)
Before the reseller could reply, I discovered that the name of the worksheet had to be the same as the named range, "Fiscal_Sets".
This requirement is not defined on page B-4 of the GL user guide.
Hold on.... perhaps my English isn't quite fluent enough, but how can one interpret "Please market all required fields" as "Change the name of the Excel worksheet to match the required named range"?
The GL user guide says nothing about the specification of worksheets required by Accpac. And this is in a section entitled, "Tips and reminders".
I have found that often the items identified with red asterisks as being "required" are not the only items that you must have to import! Please update which items are TRULY required.
yeah I have had all of the import issues as well...ever since 4.2 from memory the import errors have been really bad, the error that it gives you on the screen is usually not the actual cause of the issue..sometimes it's a real pain to try and work out what is going on.
The main cause of issues with importing IC transactions is that the Ref field must not exceed 36267 (Integer size limit).