• From: UK
  • Registered: 05/13/2008
  • Posts: 31

Topic: Journal Entry Bug and Bug in Business Partner Selection List

There is a default account code entered in the account field in the journal entry and payment entry. This is okay, but the entire text within that field should be selected when the cursor enters that field, so that it is fast to change the account code.

Otherwise bookkeeping will not be as hassle free as it should be.



In the business partner selection fields it only shows the first BP untill you search with a * and first then it will give you the complete list. I understand that you don't want to give the user a complete list by default, since this can be slow when you have a lot of bp's, but it is very confusing that it then displays just one by default.

If you absolutely need to have a default value, you could make it display the ten most used within that session.

  • joe
  • Administrator
  • Offline
  • Registered: 03/15/2007
  • Posts: 5,085

Re: Journal Entry Bug and Bug in Business Partner Selection List

Yes, you are right regarding the accounts, we will look at this during the RC period.
Rasmus, the search boxes in the BP selections are only used if you check the 'no_customer_list' or 'no_supplier_list' in the company setup. It's there if you have more than, let's say 100 BP's. Then you have the option to enable the search boxes.
Otherwise it works just like a normal listbox.
Hopefully we can publish the RC1 tomorrow. We have had some work to fix the Ajax stuff.

/Joe

  • From: UK
  • Registered: 05/13/2008
  • Posts: 31

Re: Journal Entry Bug and Bug in Business Partner Selection List

However, it still only displays one BP by default when the search function is activated. This is the list that either should be completely empty by default or only contain the most frequently used BP's.

  • Registered: 12/25/2007
  • Posts: 2,446

Re: Journal Entry Bug and Bug in Business Partner Selection List

The focus issue is fixed now in RC1. The most frequently used items in start select is good idea, but TBD after final 2.0 release.

Janusz