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.

Be able to create Generic Inquries from sql statement, view or stored Procedure

Be able to create Generic Inquries from sql statement, view or stored Procedure. Have a window that you can insert a sql query, view, or stored proc call as an option which would then exclude tables and relations. The other tabs would still be available, then you build your summary data anyway you want.
  • Guest
  • Nov 3 2014
  • Gathering Feedback
  • Attach files
  • David Eichner commented
    15 Aug, 2018 08:20pm

    I'd also like to be able to copy complex SQL into a screen and have it show the equivalent BQL.

  • Vladimir Panchenko commented
    22 Jun, 2018 11:16am

    Could you please explain this idea in more details?

    Do you want to take a SQL select / SQL view and convert it to Generic Inquiry settings (tables, relations, sorts, etc.)?

  • Tim Rodman commented
    10 Jun, 2018 04:09am

    You can already bulld a Generic Inquiry on top of a SQL View ike this:

  • Delmer Johnson commented
    3 Aug, 2015 04:21pm

     I cannot support this idea as currently written for several reasons. First, I do not understand the request. What does it mean to "insert a sql query, view or stored proc call... which would then exclude tables and relations." I honestly have no idea what that means.

    Second, and more important, many security experts would include SQL Injection attacks among the top security vulnerabilities on the internet. When you write SQL for a web site you had better know what you are doing, and people who think they do still make mistakes. There's a reason why this remains in top ten lists year after year (see

    In addition, Acumatica can run on different databases engines (SQL Server or MySQL) and SQL syntax differs between them. That's one reason why Acumatica developed Business Query Language (BQL), which represents a safer, supported alternative.

    Finally, there is no way, as far as I know, to get the current CompanyID from Acumatica, making it difficult to properly filter SQL statements in a multi-company environment. Having such a call is a necessary first step to writing a parameterized stored procedure (and stored procedures, as I understand it, are not supported by Acumatica).