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.

Add the ability to type in characters to Screen Name fields and trigger the filter display of matching names.

Version: Acumatica 2018 R1 Build 18.112.0019

Background: When creating/updating import scenarios (SM206025), we can type characters into certain fields (scenario name, provider, etc.). The benefit of doing so is that the filter will automatically display a list of matching names reducing the time of searching for the right objects. 

Problem: However, it is currently not possible to type in any character for the value  of Screen Name which obliges you to do a long navigation exercise through the tree of Screens.

Enhancement: Add the ability to type in characters to Screen Name fields and trigger the filter display of matching names.

 

Thank you for considering this enhancement.

  • Eudes Coelho
  • Oct 3 2018
  • Gathering Feedback
  • Attach files
  • Eudes Coelho commented
    October 11, 2018 10:11

    Hi Vladimir,

    I am afraid I am not familiar enough with the terminology in Acumatica to understand what "a selector lookup with the search capabilities" implies. Would you please explain ? Many thanks.

  • Vladimir Panchenko commented
    October 11, 2018 09:09

    Hi Eudes,

    Thank you for your idea. We're thinking about replacing the tree with a selector lookup with the search capabilities. Will it be sufficient in this case?