If you’re referring to the Inventory Allocation Details screen (IN402000), the ResultRecords view is defined as below.public PXSelectOrderBy<InventoryAllocDetEnqResult, OrderBy<Asc<InventoryAllocDetEnqResult.module, Asc<InventoryAllocDetEnqResult.qADocType, Asc<InventoryAllocDetEnqResult.refNbr>>>>> ResultRecords;I would override this in a customization and change the order in the graph extension class member, or in its Initialize() method to suit your needs.
Is the custom field a db field also? Is it designated as such in the DAC extension?
@aaghaei , that sounds like a good way to get around it, and the transaction prevents commit to the database for the approvals. I would of course want to test it fully to make sure not removing those approvals doesn’t affect any built in scenarios or workflows.
This is topical for us as well because we are defining our own best practices for customization packaging, publishing, and backup. I haven’t decided yet, but I’m leaning towards a readme.md (markdown) file included in the customization package, as well as being stored in our source code repository (Azure DevOps) for that customization.I don’t believe that notes on a customization project inside Acumatica will be exported into its package, so I wouldn’t recommend using notes for this purpose because of its lack of portability.
Based on what you’re describing, I might suggest some other ideas for options instead of using a database trigger: Override the method, but change the part that deletes the records. Override the method, but write the rows to a new custom table, and let the existing method remove them from the original table. Then you can query the records from the new table, and even join to the existing table.
AssignAR may be an option. Even though they were originally construction-focused, they have expanded, and we have had success working with them ourselves as a VAR. Here’s a link that may interest you → https://www.prnewswire.com/news-releases/aktion-associates-inc-announces-partnership-with-assignar-301383277.html. Sorry about the partial company plug here.😀
You can do it in the extension class with something like this: public override void Initialize(){ Base.PaymentList.OrderByNew<OrderBy<Asc<PRPayment.usrLastname>>>();}
What we’ve done to change the print order for these is to reorder the view APPaymentList in a code extension of APPrintChecks.
If you want to disable the Bill-To contact email on an invoice when it comes in empty, I believe you would want a customization created to enable/disable the email field and the Override Contact checkbox on this condition.
I’m going to post a related question on this because it is actually related to an Acumatica-owned product - Imperium.
Apparently this is happening due to a 3rd party license manager from EIS that is installed on this one instance.
There’s no issue with my script. As I said, it executes fine on many instances. The issue is the error prohibiting the customization from publishing on this one instance.
Acumatica says that the mobile app use the same web.config file as the web app, so the session timeout configuration in that file should work for both.
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.