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.

Company and Branch Variables in Generic Inquiries

The only special parameter variables that I am aware of are @Me, @MyGroups, @MyWorktree, and @Today which can be used in the CONDITIONS tab on the Generic Inquiry (SM208000) screen.

But it would be nice if we also had @Company and @Branch variables (or something like that).

Both @Company and @Branch would be needed because in 2018 R2 there aren't just Branches, but both Companies and Branches.

The Company/Branch that you have selected on the top doesn't mean that you're "logged in" to a Company or Branch. It's just a default value for any new transactions. This was made more clear in 2018 R2 by moving the selector to the top next to the Business Date which is also just a default value for any new transactions.

Even though the Business Date is just a default values for new transactions, the current @Today variable respects the Business Date.

So it would make sense to me that we could also have @Company and @Branch variables which respect the Company/Branch selector.

  • Tim Rodman
  • Oct 29 2018
  • Future consideration
  • Attach files
  • Morgan Taylor commented
    September 17, 2019 18:15

    New idea related to improving generic inquiries. Worth supporting!

  • Morgan Taylor commented
    September 17, 2019 17:59

    The ability to use a broader and richer setup of both variables and functions in setting default values in parameters would be highly useful. It would simplify many common steps by users. For instance, often reports will be run for YTD or PTD. Reports can be configured for such. However, the current tools do not allow for converting the built in data variables provided to a period value.


    I'd suggest that this idea be broadened out to include allowing functions on default values variables to provide a broader flexibility in setting default values, such as LEFT, RIGHT, CStr, etc.

  • Vladimir Panchenko commented
    November 21, 2018 08:50

    Noted. Thanks, Tim!

  • Jeffrey Patch commented
    November 03, 2018 07:39

    Great idea Tim


    Although I just tested @Today, and I cannot get it to "respect the Business Date" (see attached).- something I have raised in the past.  Perhaps my build is a little out of date.