Replies posted by tlanzer25
I’m not extremely familiar with the functionality behind this screen, but as I mentioned, you can likely override the Picked view delegate method which queries the ship lines, and add a condition to the query to only look for your new flag.
What version of Acumatica are you customizing? The WMS module was actually rewritten for 22R1, so that’s why it may be less straightforward to extend. It appears that most of the code for this is within the PX.Objects.SO.PickPackShip class, and contains mostly protected methods. The DAC header view seems to be HeaderView. What are you trying to extend in the DAC? There are delegate methods for the Picked, Packed, etc. views that you could override if you want to change the content or order of those lists.
@duanes39, I think this is either because of the filter, or the logic retrieving the next check number. I would first try to order the filter named Filter similar to the PaymentList view mentioned above, or in a view delegate. If that doesn’t work, you may need to override the TrySetNextCheckNbr() method when it is setting the next check number.
There are two possibilities that I can think of:Inherit InventoryAllocDetEnq instead of extending it. You can then override the protected virtual method naturally in the child class. You would need to specify the new class in the UI instead of the original class. Use the PXProtectedAccess class attribute on an abstract graph extension. This is a way Acumatica provides to call protected members in an extended class. Here is a link to an example: https://stackoverflow.com/questions/66568715/unable-to-use-protected-method-override-in-acumatica-graph-extension
It looks like the Filter view has a delegate method (filter()) that will also need addressed and sorted differently. You should be able to override this method, call it as its base method, then sort the results as you need them. Let me know if you want some sample code.
@ramya15, Typically with a Line Details type of dialog, I would extend the RowSelected event handler for the line details table/entity and enable the appropriate fields if they are not already. If the fields are enabled but not saving, I would suggest setting CommitChanges to True in the UI settings, and maybe extending the FieldUpdated or RowPersisting event handlers, or the Persist method, then debugging to see when the value is getting lost. You may need to force a Persist() if needed.
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.
@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.😀
Login to the community
Social LoginLogin with your Acumatica account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.