Skip to main content
Answer

Customization impact after upgrade - SOShipmentEntry

  • December 23, 2021
  • 3 replies
  • 208 views

Forum|alt.badge.img

We’re working on upgrading a Customer from 2019 R2 to 2021 R2. We do have a lot of customizations and I’m running into a few issues esp. with SOShipmentEntry graph.

After resolving initial errors in the customization code after upgrade, the code compiled and I was able to publish.

However many functionalities are not working. For e.g., looks like the events such as RowPersisted, RowPersisting, RowInserted, RowUpdated, override of Persist method etc. we already had on SOShipmentEntry are not firing anymore. 

There was also a custom tab with a grid which was not displaying and causing the entire page to break. It was giving an error that the view used by the grid is not available. Though I published multiple times, it kept complaining the same that the view is not available. When I attempted to edit aspx, got an error that Sequence contains no matching elements. I finally deleted the Shipments screen from the customization package and re-added it without the custom tab/grid.

Does anyone have any insights on what might be going on?

Thanks.

Best answer by Raj Gopinathan

Thanks Naveen. Yes, I commented out the entire SOShipmentEntry Extension file and started again from beginning with one change at a time in place and realized that it was the changes to the PostShipment method we had made. We had overridden the method which in turn invokes other protected Acumatica methods.

We tried using the new PXProtectedAccess feature but had done that incorrectly within our existing extension and to add to that mistake, probably based on Intellisense recommendation, had made the extension graph “Abstract”. How silly!!! Issue resolved after adding the additional abstract extension class for protected methods and inheriting our extension class from both the Acumatica base graph and the abstract extension class.

3 replies

Naveen Boga
Captain II
Forum|alt.badge.img+19
  • Captain II
  • December 23, 2021

Hi @rgopinathan51  Yes, there are many changes done in the 21 R2 from 2019 R2 but that will not stop firing the events. Have you commented code blocks one by one and verified, where exactly it is causing the these issues?


Forum|alt.badge.img
  • Author
  • Jr Varsity II
  • Answer
  • December 28, 2021

Thanks Naveen. Yes, I commented out the entire SOShipmentEntry Extension file and started again from beginning with one change at a time in place and realized that it was the changes to the PostShipment method we had made. We had overridden the method which in turn invokes other protected Acumatica methods.

We tried using the new PXProtectedAccess feature but had done that incorrectly within our existing extension and to add to that mistake, probably based on Intellisense recommendation, had made the extension graph “Abstract”. How silly!!! Issue resolved after adding the additional abstract extension class for protected methods and inheriting our extension class from both the Acumatica base graph and the abstract extension class.


Naveen Boga
Captain II
Forum|alt.badge.img+19
  • Captain II
  • December 28, 2021

Hi  @rgopinathan51  HAHA! 

Yeah! it might be due to the Intellisense suggestion, you may have done that change. Anyways finally identified the culprit :)  Thanks for sharing the update.