Since upgrading to 23R1, our Invoice reports are taking an extremely long time to print. It’s taking 30+ seconds to generate a single invoice. Sometimes it will take up to 2 or 3 minutes. This issue is not present in our upgrade sandbox, where performance is generally much slower all around. Printing the same invoice using the same report version takes only a few seconds in the sandbox. I’ve been working to remove unnecessary bulk from the report definition, and have seen some small performance improvements, but nothing significant. Has anyone else experienced this issue? I’m guessing that there’s nothing I can do but continue chipping away in report designer. But the drastic difference in performance between our previous build and upgrade sandbox compared to our live environment makes me think something else could be going on. Thanks!
My company would like to send out email notifications if the cost of certain items has changed.Ideally, the notification would include a table with a format similar to the following. But I have not found a way to access the “old” cost once the value in the cost field has changed.Item Code Old Cost New Cost ABC123 $1.00 $2.00 Is there any way to report the previous field value within a notification? Thanks!
I’m looking for clarification on how to configure Field Level Auditing. How do you know which Tables and Fields to select on the Audit screen? Example:I wanted to audit changes to the SALESPERSONS tab of the Customers screen, which corresponds to the “CustSalesPeople” table. I tried to set up field level auditing by selecting the relevant Table and Fields on the Audit screen, as advised in the wiki. I only wanted to track changes to the Customer Salespersons table, so I only selected that Table. However, none of my changes were tracked with this config. Through some trial and error, I was able to get the audit working by also selecting the BACCOUNT and CUSTOMER tables.Can anyone explain why I needed to select these additional tables? Understanding this would make setting up auditing much simpler in the future. Thanks!
I’m having difficulty controlling access to particular form elements. The behavior I’m observing runs contrary to the guidance provided by the Acumatica wiki and training manuals. Currently using Acumatica Cloud ERP 2020 R1, Build 20.114.0020. The wiki says that:“By default, a role’s access rights to the form elements and actions are inherited from the role’s access level to the container of form elements to which elements and actions belong.” This is echoed in the security training manual: But it seems that form elements (tier 5) actually inherit their rights from the Form (tier 3), rather than the Container (tier 4). This breaks the “hierarchy of nesting” outlined above, and makes controlling access to particular form elements much more difficult. Is this a bug, is the documentation wrong, or am I misinterpreting something? Example:Form: [Receivables -> Customer Locations] node is set to "View Only". Form Container: [Receivables -> Customer Locations -> Location] node is set
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.