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.

Branch Integrity in Requests/Requisitions

See Case 087639. If a Request is entered under Branch A, a Requisition started in Branch B can use that Branch A Request. This breaks the integrity of where the Request came from. There is no audit trail. The system should 1. not allow mixing Requests from different branches in a Requisition or 2. have a filter in the Requisitions screen to choose Branch (exactly like the field to filter for Request Class).

  • Guest
  • Nov 19 2018
  • Future consideration
  • Attach files