Tinyint values are interpreted as bool by default and the interface does not let you edit the column type

[ArnoldHueteG]

Checklist

• [ x ] I have searched budibase discussions and github issues to check if my issue already exists
• There is closed issue similar to this one: Tinyint values are interpreted as bool by default #9839

Hosting

• Cloud
  • Tenant ID: https://aritek.budibase.app/builder/portal/apps

Describe the bug
When a SQL Server table with field of type "tinyint" is imported, it is interpreted as a boolean value and the interface does not let you to change the data type.

To Reproduce
Steps to reproduce the behavior:

1. Create a table with a tinyint field in sql server, add a few values
2. Import table and see the table with all values check.

Expected behavior
The field should be integer number

Screenshots
The screenshots are above.

Additional context

For some reason the exported schema shows table with duplicated columns:

CREATE TABLE [TB_TesoreriaTipo] (
TipoID tinyint(1) NOT NULL,
TipoID tinyint(1) NOT NULL,
Tipo varchar(100) NULL,
Tipo varchar(100) NULL,
 CONSTRAINT [PK_TB_TesoreriaTipo] PRIMARY KEY (TipoID)
);

[linear]

BUDI-8735 Tinyint values are interpreted as bool by default and the interface does not let you edit the column type

[jmlaurenti]

Hi @ArnoldHueteG @ConorWebb96 , I have exactly the same issue with BB 3.5.2 and a MySQL table created outside BB: any field created as TinyInt is interpreted as Boolean, and cannot be changed back to numeric in Data view.
Side effect : when changing the field from TinyInt to Int (outside BB) and fetching MySQL Tables to ensure Budibase gets latest structure update, field is still seen as boolean. I had to change field name to ensure BB fetch takes into account the type change.

Is it needed to create a separate bug, or can this one be used to track the issue ?

Thanks!