Ideas for Acumatica

Important! Please note that 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.
This portal is for product ideas and feedback only. If you need customer service assistance, please contact your Acumatica Support Partner or submit a support case.  You can also 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. 

"LIKE" condition for filtering

For filtering, we do not currently have a "Like" condition.
This would be useful for filtering on Segmented fields.
IE

If we have these Subaccounts

US-00-10-00

EU-00-10-00

AA-00-10-US

 

It would be useful to be able to filter the Subaccount field for

LIKE ____10%

  • Angel Sanchez
  • Jun 8 2018
  • Already exists
  • Attach files
  • Vladimir Panchenko commented
    June 27, 2018 11:27

    Condition "Contains" is another name for "LIKE". Also, there are "Starts With" and "Ends With" conditions. For your example with Subaccount field you can use "Starts With" condition.

  • Angel Sanchez commented
    June 27, 2018 17:00

    "Contains", "Starts With", and "Ends With" do not do this


    This would be specifically for filtering the middle values

     

    IE
    __00____

    or
    ____10__

    Using "Contains 00" would return values that end in "00" when you're really only looking for ones with "00" in the second segment.

     

    We have this ability in BQL, it would give users more precise results if we were able to filter using LIKE

  • Craig Haseley commented
    February 06, 2019 17:47

    I found this to be a huge issue as well - I came from a system where any general ledger type report could be run by any segment or any combination of segments within the subaccount

  • Angel Sanchez commented
    April 09, 2019 20:30

    I see this issue is still marked as "Already exists"
    Just adding this comment here to reiterate that the functionality doesn't actually exist.