New Bug Encountered: Percent value in VC changes to 0.00% after a Sync

[WillowMobileSys]

This issue was originally noticed back in July but was not reported as a bug.

A strange occurance in a virtual column: I h... Questions

A strange occurance in a virtual column: I have a virtual column which does a calculation on 4 other column values. The output is meant to be a percentage (but for now, I have a decimal output). The issue is that the virtual column RESETS to 0.00 on syncronisation. I wanted to test the calculation, so putting the same calculation into a proper column, I synced the data again. I videoed the screen… the fixed column ([PercentRecycleTest] at the top) calculates and displays 78%. The Virtual co…

The problem seems to stem from defining a VC Percent type column when the values used in the calc the value are of Number type.

VC Percent column = Number1 / Number2

When entering or editing a row, the VC column calculates the value correctly. Once saved and a Sync is performed, The VC column reverts to 0.00%.

Editing row and immediately after Save, Percentage Value is correct.

After Sync, the Percent value reverts to 0.00%

[Billy_Sheng]

Thanks for Reporting John!

[Former Community Member]

What you’re seeing is the difference between integer division and regular division. At minimum, it’s a bug that you’re seeing two different results from the same expression.

The best workaround is to ensure that one of the division operands is a Decimal rather than a Number. The idiomatic way to do this would be [Number1] * 1.0 / [Number2].

[WillowMobileSys]

@Steve_Howard I agree 100% its integer division and I posted the exact same workaround in the post that re-discovered the bug.

You can also resolve by defining the numbers as Decimal with ZERO decimal digits.

And yes, the main issue is that you see two different results at different times - client calculation versus server calculation.

But also, If I may be so bold to say so, the server should “know” what data type the result is being stored in and adjust the calculation according with the most prominent intent - especially in a no/low code environment.