We have a solution that based on row changes an automatic calculation is triggered. However when a user uses the mass import/update functionality in the GUI the first insert/update will trigger the automatic calculation. THis increases the risk of a deadlock. Is there a way to detect that a user uses the GUI import/update functionality so the automatic calculation can be turned off temporarely?
Closed
Detect the use of mass import/update through GUI in flow.
+4Hey Freddy,
As far as I know there is no easy fix for this.
Perhaps you could consider moving the functionality from the trigger to a task, which could then be scheduled? By scheduling it, the automatic calculation can then be executed periodically instead of every time a record is inserted, which would fix the problem. The only downside being that the calculation is not executed immediately, but might be slightly delayed.
+16Renée Evertzen wrote:
Hey Freddy,
As far as I know there is no easy fix for this.
Perhaps you could consider moving the functionality from the trigger to a task, which could then be scheduled? By scheduling it, the automatic calculation can then be executed periodically instead of every time a record is inserted, which would fix the problem. The only downside being that the calculation is not executed immediately, but might be slightly delayed.
It's already a delayed calculation, but the mass insert/update is a per row functionality and it takes longer than the interval for the calculation.
Can you turn this into an idea?
+23New→Open
+9Unfortunately, this idea has not received many votes. Because we want to keep the focus on ideas that are in high demand in our Thinkwise Community, we are closing this idea.
+9Open→Closed
Reply
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.