Bug with Number Field in Row details

[athom]

Are you using our SaaS platform (Baserow.io) or self-hosting Baserow?

SaaS

What are the exact steps to reproduce this issue?

Hi,

I created a field of type “Number” (see screenshot).

When I modify its value for a row in a “Grid” view, everything works correctly.

However, when I open the row details, the value that appears in the modification history is the one I entered, multiplied by 100. Yet, the original value is displayed in the field.
Then, if I refresh the page, the value multiplied by 100 appears in the field, and in the history, the value multiplied by 10,000 appears… it’s strange.

Could you help me?

Thanks,
Adrien.

Attach screenshots, videos, or logs that demonstrate the issue.

[cwinhall]

Hi @athom, welcome to the community!

You have certainly uncovered quite a bug here and I have created an issue for it immediately on gitlab (Viewing a detailed record with a number field using comma separator changes the value automatically (#3601) · Issues · Baserow / baserow · GitLab) and I have alerted the team to this too internally.

Thanks for your detailed report it was easy to reproduce the issue!

[be_Berlin]

Is it possible that this is the same problem that I have [here] ?(Strange behavior with decimals (in Zapier and n8n): UPDATE a row works correct (125.0 is 125.0) but INSERT row is wrong (125.0 is 1250.0) - #6 by be_Berlin)?

There it gets multiplied by 10 but I think this is due to the number of decimals that are applied to the number field.
@joffcom do you think these problems are connected or even it is the same?

[cwinhall]

The issue has already been resolved and the patch will be available soon

[athom]

Hi Colin!

Any updates about this issue?

Thanks,
Adrien.

[cwinhall]

Hi @athom, the issue was patched the same day. Unfortuantely it looks as though that specific gitlab issue did not get updated. I have created a comment and linked to the gitlab issue that was linked to the patch and marked it as closed.

[athom]

Hi @cwinhall, the issue is partially fixed. The field in the row details view behaves as expected now, but the value displayed in the modification history is still multiplied by 100.

Thanks,
Adrien.