Adding item description to an .IMP file

SUGGESTED

I'm trying to programatically construct  IMP files using an external program, however I can't figure how to include the item description.

Is is possible to do so, or what would be the alternative to acheiving that? I'm getting the IMP specs from this page:
support.na.sage.com/.../viewContent.do

Parents
  • 0
    I can't figure how to include the item description.

    As far as I could tell, the import format doesn't allow for importing descriptions.  

    My impression is that Sage intended that functionality to provide integrators a way to record the bare essential details from an external invoicing or POS system (item code, price, sales tax, payment method, amount owing), rather than producing complete invoices to be printed and sent from Sage 50.

    The Sage 50 SDK has more capability, but of course is also more complex to learn and use.  The sample file in the c# folder shows how to feed in richer invoice data than the bare-bones .IMP import file allows.

  • 0 in reply to RandyW
    SUGGESTED

    Hi, 

    Thank you for answering.

    In my case that means I can't do it directly in Access VBA, I have to switch to C# .NET. Eveything else I needed was included in the IMP format. It's difficult to understand the decision to exclude only one field.

  • 0 in reply to frabora

    It's also possible to create an invoice by directly creating invoice records through an ODBC connection, so it is certainly possible to do it with VBA.   The SDK explains the basic creation of a record and incrementing the lastID tables, and there is a data dictionary.  It's better than writing Assembly code, but not much, as there would be a LOT of coding and some reverse engineering required.

    Given the time the other options take to implement and test, you probably want a third-party import utility that can import more invoice fields.  

    It's difficult to understand the decision to exclude only one field.

    I think the import was only meant to be an absolute bare-bones get-it-working at the start, to be enhanced later, and the project lost all momentum since. 

Reply
  • 0 in reply to frabora

    It's also possible to create an invoice by directly creating invoice records through an ODBC connection, so it is certainly possible to do it with VBA.   The SDK explains the basic creation of a record and incrementing the lastID tables, and there is a data dictionary.  It's better than writing Assembly code, but not much, as there would be a LOT of coding and some reverse engineering required.

    Given the time the other options take to implement and test, you probably want a third-party import utility that can import more invoice fields.  

    It's difficult to understand the decision to exclude only one field.

    I think the import was only meant to be an absolute bare-bones get-it-working at the start, to be enhanced later, and the project lost all momentum since. 

Children