Forum Discussion

GRSeach's avatar
GRSeach
Experienced User
10 months ago

Error 28, "Item is not sold" when importing item sale from CSV

AccountRight Premier v19.16 (19.16.1.225770).   I'm a retired VB developer who's been asked to automate invoice creation in MYOB, from a bunch of Excel sheets.   In Excel VBA, I've extracted the ...
  • gavin12345's avatar
    gavin12345
    10 months ago

    Hi GRSeach 

     

    Your opening comment indicated you were using v19.16 - please confirm, as this error is more common with AR2024.

     

    Also rather than providing snippets of info, attach the import file and the importlog file which shows what transaction caused the error. Importing is a complex process, and the slightest thing can cause an error.

     

    Suggest you also go through the tax codes and ensure every tax code that you use have a linked account for tax paid and tax collected.

     

    Regards

    Gavin

Mike_James's avatar
Mike_James
Ultimate Cover User

Hi GRSeach , I've attached sample export files from an AR2024 file, because even the order of fields can generate that error message.

 

Personally I prefer the tab-delimited format. Commas in addresses can mess up the import.

If working in Excel, amounts should be formatted as numeric, no dollar sign or commas, which Excel messes up when saving as txt.

Fields you don't need can be excluded.

You can import multiple sales in one file as long as there is a blank line between each transaction. 

GRSeach's avatar
GRSeach
Experienced User
10 months ago

Hi Mike_James , thanks for replying. I appreciate it.

 

I had already removed commas and apostrophes while extracting the source data, so comma-separated is fine.

 

I stripped out most unused columns. Here's what's left. I got the same error.

 

CoLastName, FirstName, AddressLine1, AddressLine2, AddressLine3, AddressLine4, Inclusive, Invoice number, Sale date, CustomersNumber, ShipVia, DeliverySta tus, Item number, Quantity, Tax code, SaleStatus

RH US LLC, , , , , , X, 1/09/2024, 4522971, , B, PIANOX_62GR, 2, EXP, O

 

Graham

 

  • Mike_James's avatar
    Mike_James
    Ultimate Cover User
    10 months ago

    Hi GRSeach , the headers and data go out of alignment at Inclusive. Add another comma after the X and it should be OK. Also watch out for leading or trailing spaces, eg remove the space before 1/9/2024.

    • GRSeach's avatar
      GRSeach
      Experienced User
      10 months ago

      Hi again Mike_James ,

       

      That can't be right; after Inclusive comes InvoiceNumber, then SaleDate. In the data, I have "X" for Inclusive, blank for Invoice Number, then the date.

       

      Inclusive, InvoiceNumber, SaleDate

      X.             ,.                            , 1/09/2024

       

      Graham

      • GRSeach's avatar
        GRSeach
        Experienced User
        10 months ago

        Hi Mike_James ,

         

        Sorry, I see it now. That's actually a typo in my message. The actual values include 2 commas, not 1.

         

        Graham

Looking for something else?

Search the Community Forum for answers or find your topic and get the conversation started!

Community home

Dig into MYOB Academy for free courses, learning paths and live events to help build your business with MYOB.