Row-Update Causing Browser to Freeze

Trying to complete a basic customization for PO Entry, I am about 90% of the way there, however a basic row-update widget seems to be triggering some sort of continuous loop causing the browser to freeze. The short version of the customization is that in PO Entry, I’m doing a basic event to populate the Incoterm Location text box, based on the Incoterm location saved in the Vendor Purchase Point table for the PP being used in the PO. The ultimate goal is simply to save users from entering the same info for each PO to the same vendor/pp. My event is being triggered each time the vendor ID changes or Purchase Point changes. My event does a simple rest-kinetic call to Erp.BO.VendorPPSearchSvc → GetByID, the response goes into the actionResult dataview. So far, all of that works as expected, confirmed with a trace. I then have a condition to understand if LocationEnabled = true, and if so, I am trying to populate the IncotermsLocation field via row-update. When the row-update executes, it causes the browser to freeze, if I wait long enough, I get the “Long Running Process” slideout. I’ve tried the following with no luck:

  • Disable View Events → Row Update → Enable View Events (thinking maybe there was a loop being trigged by dataview change trigger
  • Changing my row-update to the PO Header CommentText field, on the off chance updating location field was triggering something (even though nothing shows for this field change in the trace)
  • Creating a different Dataview to store my returned dataset (VendorPP) in the event I was wiping out something in actionResult dataview that the system was looking for in a different event
  • Closing layer, closing out of the system, clearing cache, re-testing
  • Creating a new layer, starting from scratch (all of this is building off the standard layer by the way, not working off of an already customized layer)

Nothing evident in the browser trace, no error logs after my row-update, the row-update event in the console shows the correct value being assigned to the location I want, nothing in the network tab in terms of continuous method calls or other processes running out of the normal or continuously. Once the row-update runs, I can’t scroll in the browser, I can’t call up the views to see if the value changed, and the value does not populate in the text box. I have to refresh browser, or close out. Any ideas are more than welcomed!

1 Like

Why not use a bpm if you are just trying to default in the value from the purchase point? It could be done when vendor or pp has changed from any to any other.

3 Likes

Thanks Alisa. Yes, that’s ultimately what I’ve steered toward. Actually, because there are two methods that could cause this to change, I’m doing a function call to change the value. I was just thinking a basic app layer should do the trick, but of course it’s not that straightforward. I have a ticket in with support, we’ll see how that goes.

I am encountering this issue now.

It looks like in the row-update, if I add an additional column, to a parameter it screws up.

If I add an additional parameter, then a column to that, it behaves.

Again, I am unsure lol.

2 Likes

EpicCare apparently determined if you are creating an event with a row-update, and you complete the configuration of the row-update widget without navigating away from the event before fully configuring, it will work? I haven’t tested this; I just ended up doing things differently. There is a problem number associated now though.

I have experienced a lot of issues with Row-Update. One thing I noticed if I add a column to an existing parameter. save and close the event. Then go back in I have 2 parameters the first has one column filled out and the second is blank then the second parameter has the completed column I originally added to the first column. I don’t believe you will notice an issue until you expand the row update param and see the blank. This for some reason stop all the processing of future events.

1 Like