Forum Discussion

Mike_James's avatar
Mike_James
Ultimate Partner
13 days ago

Import of item allows blank values for number of items per selling unit

In the core program, an item cannot be created without a non-zero value from 1-9999 for the number of items per selling unit. (Buying unit is presumably the same).

 

If a value of zero is supplied during import, it is replaced by 1, with a warning. However, I have noted in a client's file a number of instances where this value is blank, and I understand these items were imported via the import/export wizard. I tested this per the attached to prove the theory.

This has adverse implications for data integrity, inventory management, sales reporting etc.

 

Once an item has been used in transactions, this value cannot be changed, so the client is stuck with these errors.

 

Even if this issue is confined to this one file, it still needs investigation and correction. Please assist.

  • MikeG1's avatar
    MikeG1
    12 days ago

    Morning Mike_James , I can confirm that this has been verified as a bug and has now been raised with the devs. I wont be able to provide any ETA at the moment but will do my best to keep this thread updated if I see any progress. Cheers, Mike

  • MikeG1's avatar
    MikeG1
    MYOB Moderator
    12 days ago

    Morning Mike_James , I can confirm that this has been verified as a bug and has now been raised with the devs. I wont be able to provide any ETA at the moment but will do my best to keep this thread updated if I see any progress. Cheers, Mike

    • gavin12345's avatar
      gavin12345
      Ultimate User
      12 days ago

      Hi Mike_James and MikeG1 

       

      A word of caution, if I may. I noted an absence of any reference to the use of I Inventory, or that the Item is inventoried - though this might be inferred from the context.

       

      Number of Items per Buying Unit and Selling Unit SHOULD be NULL unless the Item is inventoried. Otherwise users will get the Error 4077 error preventing update via import and constant requests for MYOB moderators to run the 4077 script over the file will continue. The script sets Number of Items per Buying Unit and Selling Unit to NULL, allowing update via import.

       

      So yes if the imported item is to be Inventoried, Number of Items per Buying Unit and Selling Unit should be set (or default to 1). Developers should fix this if it is not doing this.

       

      The important and more prevalent bug the developers need to fix is that when you create a new item with I Sell and do not use I Inventory, MYOB sets Number of Items per Selling Unit to 1 - it should not, it should remain as NULL, as it does for I Buy. This bug is triggering the error 4077 every time a new sold item is added which is not being inventoried. FYI the Number of Items per Selling Unit is not displayed on screen, even though it has been added to the database. Contrary to comments by moderators, the error 4077 issue is not caused by a user changing the item settings after creating the item, the issue is caused by MYOB itself when the item is first created.

       

      To confirm - you cannot use a clearwater file to confirm it works as this already has error 4077. Create a new file, and add one item and set to I Buy and I Sell only. Do not set Number of Items per buying unit or selling unit - this field should not even appear. Create a customer card and process a sale transaction for this item. Then try to import a new price for this item - you will get error 4077 - even though the Selling Details screen does not show the Number of Items per Selling Unit field. Run the error 4077 script over the file - this will clear the Number of Items per Selling Unit and you can then complete the import to update the price.

       

      Regards

      Gavin

       

       

      • MikeG1's avatar
        MikeG1
        MYOB Moderator
        11 days ago

        Thanks gavin12345 - that is valuable context and a clear explanation of what is contributing to the 4077 error. I have ensured that this is added to the ticket with developers for consideration. Hopefully it will be possible to address all of this!

  • MikeG1's avatar
    MikeG1
    MYOB Moderator
    13 days ago

    Hey Mike_James , thanks for raising this
    I will ask our product specialist team to try and replicate the testing you have done and then log this with our developers.
    Based on the info you have provided it seems like it could be a bug but will need to raise it through to the right people.
    Thanks!

    • Mike_James's avatar
      Mike_James
      Ultimate Partner
      11 days ago

      Hi MikeG1 , gavin12345 , thank you both for your comments. Unfortunately I have had no email feedback to my original post, until a prompt came in overnight to ask if I got the answer I needed :(...

      I'm glad to know this has been put forward as a bug, so I will mark your post as a solution Mike, but I hope Gavin's comments will be included. I look forward to the resolution being mentioned in a future release note.