Pricing Import 4077 Error

Hi GD-mt,

Appreciate for providing the details. If this happens, please reach out to our back-end team directly, as we no longer have the tools on the Community Forum to fix it. You can reach our Live Chat team via our virtual assistant, MOCA or by submitting a support case via MyAccount.

Regards,
Earl

Hi Earl, I am also struggling with issue. 
    - Support request is 60 hours old, not reviewed.  Previous unrelated support request is over 10 days old and not reviewed.
    - 1300 555 123 number does not work - iphone keystrokes do not register during call, so I can't dial '3' to get to next menu.
    - "Priority Support' booking page does not work, "Something went wrong, Booking has failed. Please try again later".
    - I am currently 'on hold' with MOCA, but not bursting with hope.

The "Error -4077" has been an issue for years now.... why can it not be fixed permanently?  Every time I have done an Item Sales Price update I have to go through this misery, but at least in the past it could be fixed in this forum.

Hi Alex, 

I lodged a case through support which I then had to follow up as it was not actioned after 2 weeks. I then spoke to someone through the MOCA chat to find out I couldn't get this request actioned due to not being an admin on the account and having authority. I eventually had it resolved with an admin on our account having to get it actioned for me. 

I too have always had the problem resolved from this forum in a very prompt timeframe. I don't understand either why it can't be a permanent fix or why you have to be an admin on the account. It is really painful to have the script run every time a pricing import is done. 

Hi GD-mt​ , AlexUldis​ , the 4077 issue was explained in a forum post in 2025 (Import of item allows blank values for number of items per selling unit | MYOB Community). It was put forward to the developers as a bug, along with manual imports of new items allowing a blank for number of items per selling unit. Unfortunately these significant bugs have not been fixed. The explanation went as follows:

"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".

Since MYOB moderators can no longer fix this or any other issues , contacting support is your only option. Requiring an admin user to make a request for a fix is a new constraint.