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 2, 2023

Thanks for the quick reply @GeorgiaC - if only your techies were as responsive, we wouldn't have problems like this!

 

I tried the Live Chat route last week - https://quickbooks.intuit.com/learn-support/en-uk/transactions/re-bug-in-qbo-making-data-entry-slow-extremely-annoying/01/1263978/highlight/true#M21116 - the agent I dealt with claimed they have no such magic wand & referred me to... the Cog Wheel of Doom, the place where Feedback goes to die.

 

In essence, if/when a developer deigns to read the feedback, deems it worthy of their valuable time & decides to action, then (& only then) will I receive an update.  I have not received an update so I assume that nothing is being done & nothing will be done unless more noise is made.

 

If we were asking for some fancy new pie-in-the-sky feature, I'd understand the delay.

We aren't.  We are simply asking for the bad coding to be reversed.  They've done it once so it shouldn't be too difficult to do again.

June 26, 2023

This really does make for a tedious experience.. Why can't this simply be corrected? Is it supposed to function this way? If not, is there anything users can do to fix it?