Topic Options
#1845 - 01/11/02 09:03 AM Importing batches into G/L
bd Offline
Adagio Guru

Registered: 11/29/01
Posts: 102
Loc: Peterborough, ON
It was suggested to me that when preparing a batch for importing through Excel to save as a .csv file (for MS-DOS). When I do this I still don't get the quotes around string fields that the ACCPAC Plus 6.1 manual suggests. The only batch I've successfully imported into ACCPAC or Adagio is a .csv file that I edited using the DOS editor and put in all the quotes and reformatted the dates. Has anyone had similar problems, or if you have imported, how did you prepare the file.

Is anyone using giftTRAQ to export batches to ACCPAC or Adagio? If so, is it working and what file format is it?


Top
#1846 - 01/11/02 11:07 AM Re: Importing batches into G/L
Softrak Support Offline

Adagio Action Team

Registered: 03/09/99
Posts: 11543
Loc: Vancouver, BC Canada
Dear bd

Are you exporting the file from another application? If so, if you choose .csv as the file format, it should do everything necessary to format it correctly.

The trick to a successful import in the destination application (i.e. Adagio) is to ensure that:

1. Every field that is in the file you have exported from the source application is represented (i.e. If you have exported 12 fields, you must format your Adagio import template to have these same 12 fields).
2. The Adagio import template must represent these fields in the same order they appear in the file.
3. If the file itself includes all the necessary (default) fields that are required (i.e. Record type, Entry number, Fiscal period etc...), you should not have any fields selected in the Adagio import template's 'Field Defaults' screen. This area is reserved for imports that do not contain these fields, and when used tells Adagio to use the default information set up in the destination database.
4. The fields in your source file should be of the expected 'type' as indicated in the Adagio import template. For example, the GL Record Type is a Number with a width of 1. You have no option to change this in Adagio, so your source file MUST adhere to this format. The Entry Number field on the other hand, can be a Number format with a maximum width of 6, or a String format. If one the fields in your file is a certain 'type', and you cannot modify it, then you must modify the field in your Adagio import template to match that type.
5. Adagio does not import header lines. If there is no option in your source application to omit the header lines, then you can edit the file, but it would be advisable to do so in a text editor, and NOT Excel - unless you can save it successfully as a .csv or as a .txt format. Saving it in Excel format will not work.

If you have exported the information from an existing Adagio database as a .csv file, then Adagio should format it as required. In this case, you must pay special attention to the rules above in order to be successful.

I am aware of no outstanding issues regarding this function, so there must be something that does not match up between the exported file and the import template, or a default (required) area of the destination database has not been set up yet.

Hope this helps. If not, please issue another post and tell us exactly what fields are represented in your 'export' file, what type of fields they are designated as and what exact order they are in and supply the same information
for your Adagio import template, along with details on what other options you have selected in the Adagio import screen. If you used Adagio to export the file - please also include info on what options were selected at time of export.

Thanks


Top


Moderator:  Christa_Meissner 
Who's Online
3 registered (Sudhakar, Salman, 1 invisible), 88 Guests and 0 Spiders online.
Key: Admin, Global Mod, Mod
Forum Stats
1865 Members
5 Forums
14465 Topics
70653 Posts

Max Online: 432 @ 01/20/25 10:17 PM
April
Su M Tu W Th F Sa
1 2 3 4 5
6 7 8 9 10 11 12
13 14 15 16 17 18 19
20 21 22 23 24 25 26
27 28 29 30