Ideas for Acumatica

Feedback processing: We do not reply to all messages, but we do read them, analyze them, and work to improve Acumatica based on the feedback we receive. Ideas and comments may not appear immediately. Some legitimate ideas are flagged as spam and will be added when we review the spam folders.
Content: This portal is for product ideas and feedback only. If you need customer service assistance, contact your Acumatica Support Partner, submit a support case, or get assistance from community resources: LinkedIn Group or StackOverflow
No Reliance: Information is maintained on a best-efforts basis and may be changed without notice. Acumatica cannot guarantee the accuracy of the information provided or guarantee completion of features/ideas described on this portal.

Subaccount lookup in "Account Details" screen doesn't work

More of a bug report than a feature request (in my opinion ):  In the "Account Details" screen, the "Subaccount" selector doesn't seem to work as it should; it doesn't allow searching/reviewing of available/possible subaccounts, even though it displays the little magnifying glass picture and brings up a pop-up when it's clicked (the new window doesn't show any available subaccounts and doesn't allow for any searching or reviewing of subaccounts).


EDIT:  Mods, please delete this.  I've been informed that this was, indeed, a bug in a prior version of 2018 R1, and has since been fixed in a subsequent version.

  • Geoff Hague
  • Sep 2 2018
  • Rejected
  • Attach files
  • Geoff Hague commented
    29 Nov, 2018 06:03pm

    Another edit:  Turns out this hasn't been fixed, and as per some info relayed by our Acumatica partner, he was informed this was intentional.  Seems strange... why not allow the subaccount field in Account Details to be searchable in exactly the same way that the Account field is searchable on the same screen, and in the same way that subaccounts are searchable in many other parts of Acumatica (such as when entering lines in an invoice or journal entry)?

  • Olga Anisimovich (Product Manager Financials Team) commented
    13 Sep, 2018 07:28am

    The described issue has been fixed in 2017R2 Update 10 and in 2018R1 Update 5.