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. 

Upgrades Should Not Break Native Functionality

When upgrading Acumatica, if a native feature is being replaced with another feature, then the expected behavior would be that these features continue to work after the upgrade with little or ideally no user intervention.  This is not the case, and has happened more than once during an upgrade.

An example of this is the new Labor Cost Rates screen that was added.  This replaced the employee rates that were entered on the Employee screen.  We use project accounting heavily, and after upgrading, we had to manually re-enter all of this information.  All of the data was lost after the upgrade.  Luckily, we upgraded our sandbox first and tested and realized the problem.  We still had to figure out how to manually export the data from the old version and import into the new version.  This is very frustrating.

  • Art Ardolino
  • May 2 2019
  • Already exists
  • Attach files
  • Rick Baccari commented
    May 02, 2019 16:50

    It would be prudent to survey partners and their users when major changes are being made to determine if there is a chance the change may affect them.

  • Admin
    Feedback Admins commented
    May 17, 2019 15:59

    @Art. Thank you for bringing this matter to our attention. The upgrade to 2019 R1 should automatically populate the labor cost rates screen with data according to the process on this help file: We will investigate why this did not happen.

    With each release our goal is to create software which does not break existing functionality or create additional data entry work. If breaking changes are absolutely necessary, we publish them in the release notes to make people aware of potential issues.

  • Joel Gress commented
    May 17, 2019 16:11

    There are other examples of native features not working the same after an upgrade.  AR Statements changed between 6.x and 2018 R2.  When a statement date of the 1st was selected and the preparation date for the statement was the 14th, the statement would included open invoices created prior to the 1st and payments recorded up until the statement preparation date.  Post upgrade, the statement includes all transactions up until the preparation date (new invoices and payments). 

  • Art Ardolino commented
    May 17, 2019 17:28

    Thanks.  FYI I did file a support case about the labor cost rates, and I was told that they didn't transfer and was recommended to submit and idea here.  Now that I know its supposed to transfer, I will re-open that support case. Thanks!

  • Olga Anisimovich (Product Manager Financials Team) commented
    May 22, 2019 20:05

    Hello Joel,

    In 2017 R2, we have reworked AR statements. In previous versions, AR statements of the Open Item type included documents created before and on the statement date with their open balances on the preparation date. This led to the issue that the Amount Due printed on a statement depended on the preparation date and could be different from the customer balance as of the statement date.

    Starting from 2017 R2, the Open Item statements include documents created prior and on the statement date with their open balances on the statement date which we calculate based on the payment applications. No documents with dates later than the statement date should be printed on the statements. Please submit a support case if the statements you prepared include future documents and attach a screenshot with the statement that shows the statement date and the document dates. If you have customized the Customer Statement report, please indicate this in the case.

    Thank you,

    Olga Anisimovich

  • Joel Gress commented
    September 19, 2019 11:36

    Here is another break caused by an Acumatica Upgrade. In version 6.x when project billing was processed it would create an AR Invoice.  On the AR Invoice detail lines the Billing Status field could be used to set a transaction as already billed.  You could then remove the line that you did not want to have billed from the AR Invoice and it would be marked as billed in Project.  With the introduction of the OPTIONAL feature to perform Pro-Forma billing from project, this feature/function was removed. 

  • Michael Wansor commented
    03 Jan 19:15

    In a similar thought an marketplace integrator should have to list what screens/functionality may be impacted if a user decides to add the product as a customization.

  • Michael Senter commented
    10 Feb 14:15

    Similar as we use project accounting heavy load and after upgrading, we had re-entered all of this information manually.  All of the data was lost after the upgrade.  Luckily, we upgraded our first and tested the sandbox and got the problem.

  • Michael Senter commented
    10 Feb 14:17

    Similar to use project accounting in a heavy mode, and after upgrading, we had to manually re-enter all of this information.  All of the data was lost after the upgrade.  Luckily, we upgraded first and tested on the sandbox and realized the problem.