Formula Calculation Overwrite Issues in Reports

  • 0
  • 2
  • Question
  • Updated 2 years ago
  • Answered
  • (Edited)
I have currency calculated fields within a form that self populate based on hourly amounts entered into other fields. When editing the data entry, all fields calculate and total correctly.

As an example: ([January (B) Hours]+[January (NB) Hours])*[Client Billable Rate]

However, when Grid Editing a Report that contains those same fields, the initial currency field calculates correctly based on the hours entered, but when subsequent hours are entered into other subsequent monthly fields, they calculate correctly, but then previous currency field(s) zero out. 

I'm at a loss as to why. 

Any guidance and\or help understanding would be appreciated. 

Photo of Steven Chapman

Steven Chapman

  • 80 Points 75 badge 2x thumb

Posted 2 years ago

  • 0
  • 2
Photo of Dinesh

Dinesh

  • 494 Points 250 badge 2x thumb
Yes, QuickBase formula calculation gets reset in Grid Edit view if the calculation is happening in another calculated field. But, all formula field values get set properly when grid changes are saved.

Only thing is that the result cannot be checked for all calculated fields simultaneously before saving.

There seems to be a bug in Grid Edit view formula calculation.

Regards, 
Dinesh V
Photo of Matthew Neil

Matthew Neil

  • 31,698 Points 20k badge 2x thumb
Try only having one 'calculated' field on that grid edit report, and see if it has the same issue.   Maybe one that combines all the hours, just so you can at least see that one growing as you add more entries.
Photo of Dinesh

Dinesh

  • 494 Points 250 badge 2x thumb
It's already very clear that calculation works only with one calculated column, but that would not be the usual business scenario.

We need the grid edit to do calculation the same way as it happens in the form flawlessly.
Photo of Dinesh

Dinesh

  • 494 Points 250 badge 2x thumb
The QuickBase support team has acknowledged it as a bug. Here's the reply received. Hopefully, the bug gets fixed in the upcoming releases.

The issue is identified as a bug filed under QBE011158. This bug has been logged with our developers as an issue that needs to be looked at, unfortunately, we do not currently have an ETA for a possible fix or patch.