Giving more Running Transaction time while save a record

[subbarayudu]

When I save a record (Vendor risk issue), it's taking lot of time even though internet speed is good. I'm getting a Running Transaction message on the top along with the time in seconds. Here i found the BR which effect the this Running Transaction time.

Could you please let me know what needs to be done in the BR.

After insert and update on BR on --- 'sn_vdr_risk_asmt_issue' Table

[Community Alums]

Hi @subbarayudu ,

To determine what is taking so long, start by going to System Logs> Transactions and see if you can identify anything running for a long time (about the time you canceled the timer.)

Also, Please navigate to Active Transactions (All Nodes) and then you could find the list of current active transactions and time taken by each.

Mark my answer correct & Helpful, if Applicable.

Thanks,

Sandeep

[Kalaiarasan Pus]

I dont know what you are trying to do but whatever you are doing seems incorrect. You are querying all the company records and updating the count for each record in every update. Is that what you are trying to do?

[subbarayudu]

The field "Open Issue Count" would calculate the number of Vendor Risk Issues
where the Status(state) field is not in Closed Complete, Closed Incomplete, or Closed Cancelled) and populate that row count value in core-company form.

[Kalaiarasan Pus · Accepted solution]

I am guessing you need to add this line before first query so that you can get the corresponding company only instead of everything.

gr1.addQuery('sys_id',current.vendor);