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.

MUI make the "Order" field an Int

This is in regards to case #073670


The reported issue was that when reordering screens in the MUI, some division logic was applied to make the Order value smaller when moving up, and the Order value bigger when moving down. This occasionally causes the numbers for multiple MUIScreen records to be the same, thus you can move neither screen.

This would be easily resolved by making Order an int rather than a real. We already have logic for an Order field in one of our own tables that works perfectly with Order being an int.


A newer noticed issue is that when Order is not a whole number, during a publish, some odd interpretation error happens with the project XML on the first existing decimal point in regards to "Order" thus causing the publish to crash.


We have had to manually edit the XML to not have decimals several times in several of our projects in order to allow publishing.

  • Angel Sanchez
  • Dec 17 2018
  • Attach files