what is the correct version # for 2017.2

i tried to import

<Version>
"24001","1"
</Version>
<PurInvoice>
"Staples"
"3","","2","01-31-2017","3","Debit","283.89"
"Supplies","1","","270.40","GST","0","1","5.000","13.52"
</PurInvoice>

and i get an error - line 2 incorrect version

but thats the version per the documentation - what am i missing ?

  • Try 12001.

    If it works, then you are missing undocumented bugs.
  • thanks - 12001 works fine, now what bugs am I missing ?
    maybe the one where a sales invoice can be imported as paid, but a purchase invoice cannot ?
    or maybe the one that allows you to import the sale / purchase invoice description, because that would never hold important information

    I am convinced that sage-the-company does not use sage-the-product - because if I was the sage CFO and my staff could not do their job ---- it would take the development team mere hours to fix the problems
  • The bug you are missing is that the proper version number doesn't always work for all the imports.  I think 9001 (the first version you can import) still works for some but I think because of the changes to the General Journal entry imports to activate departments, it became antiquated at the 12001 version.

    The other "bugs" are not bugs, the program for those options is working as designed.  I created an import program years ago that imported using the Sage import method and then mass updated the descriptions after.  You forgot to mention the importing of postal codes is not in the correct format.  Now to me that one is a bug.

    Roger L said:
    I am convinced that sage-the-company does not use sage-the-product - because if I was the sage CFO and my staff could not do their job ---- it would take the development team mere hours to fix the problems

    You are quite right, they use SAP.

  • Roger L said:
    I am convinced that sage-the-company does not use sage-the-product

    Methinks they would not very much enjoy eating their own dog food.

    You may already know about the free Sage 50 SDK, the C# sample in the SDK has routines for creating records and some transactions (except payments).   You may be able to make your own (although it's a fair bit of work, and you'll have update the SDK and recompile for each version).