You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It used to be the case that if a row could not be calculated because of incorrect values, evaluation of the rest of the table would continue (see rows 2475 and 2479 in the screenshot below, calculated a while back). Probably since updating to version 0.22.0 this does not happen any longer. My developer console shows Uncaught Error: [DecimalError] Invalid argument: ?.
Describe the bug
It used to be the case that if a row could not be calculated because of incorrect values, evaluation of the rest of the table would continue (see rows 2475 and 2479 in the screenshot below, calculated a while back). Probably since updating to version 0.22.0 this does not happen any longer. My developer console shows
Uncaught Error: [DecimalError] Invalid argument: ?
.To Reproduce
Caluclating
results in
Uncaught Error: [DecimalError] Invalid argument: b
Expected behavior
or possibly
Screenshots
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: