Skip to main content

Get 50% OFF QuickBooks for 3 months*

Buy now
Switch to QuickBooks and 70% off for 3 Months
paul72
Level 6
June 2, 2023
Question

Bad Coding Making Data Entry Slow & Extremely Annoying

  • June 2, 2023
  • 1 reply
  • 3 views

I think this is now four weeks since this bug (re)appeared & still no admission, never mind any action!

(the following is copied/pasted from a previous thread that got nowhere, so I'm not holding my breath)

 

The previous (correct) operation was this...

New Bill / Expense / Invoice / Cheque - the top left box (Supplier / Customer / Payee) was already active, i.e. the cursor was in there ready to type the name.

 

Current (wrong) operation is now...

New Bill / Expense / Invoice / Cheque - the top left box (Supplier / Customer / Payee) is not active, i.e. the box must be clicked before entering the name.

 

Please re-instate the previous code.  From a data-entry / productivity point of view the new operation is so much slower - it makes QBO an absolute pain in the a**e to use.

Why have a keyboard shortcut (ctrl.alt.s) for Save & New when you then have to reach for the mouse to click a box before you can enter anything on the new transaction?

 

Oh ... & if this wasn't irritating enough, the same applies DOUBLE for the Product/Service & Category columns. One click - nothing. One click just highlights the row. You have to click TWICE before you can type into the Product/Service or Category boxes.


WHY?!

 

It makes entering transactions into QBO so much slower than it needs to be / used to be.

Please, please, please revert to the old code / operation & stop fiddling with things that aren't broken!

 

This is basic user experience.  You open a form (for data input) & the first box/cell should be live & ready to accept input but it seems that UX does not mean User eXperience at Intuit/Quickbooks.

Maybe it's Users eXpendable?

How about Users eXasperated?

 

Root causes: Constant tinkering, poor coding & woeful quality control at Intuit/Quickbooks.

Quality Control Rule #1 - never implement new code if there's even the remotest chance that it's going to break something.

Short version: If it ain't broke, don't fix it!

 

Links to add some context if anyone at Intuit cares to look into this...

1 reply

Level 13
June 2, 2023

Hi paul72, we understand the delay in data entry that changes such as this can cause and it's our aim to make the overall process easier for you. So that we can ensure your request to populate the cursor in payee field automatically is reported to our technicians, please begin a direct chat. Our agents will then be able to escalate your case and keep you updated along the way. 

paul72
paul72Author
Level 6
June 26, 2023

Hi @GeorgiaC @Ashleigh1 

 

This is clearly something that is causing huge frustration to a lot of users.

We need QBO to be easy & efficient.  This bug is is slowing us all down.  It makes QBO an absolute PITA to use for manual entry.

 

The bug has been reported here many times.  It is clearly a coding problem.

Most of us have submitted Feedback as suggested but no-one has reported receiving any response.

Several of us have used the Live Chat - all to no avail.

 

Could you give us a straight answer to a straight question please?

Is this being investigated?

At all?

By anyone?

Anywhere?

July 12, 2023

Thank you @GeorgiaC 

I have replied to the email with some details.  Please let me know if you need any other information.

 

Now we have a case reference number, what does that mean in practice?

How long till this might be reviewed?

What is the general progression (how does the escalation process work)?


This glitch is still not fixed!    Although, weirdly enough, it's fixed in ONE of my client's files, but no others.  I'm stumped.