Forum Discussion
BUG::UI inconsistent data type display in lakehouse table view
ISSUE:
Data type not displayed to the left of one column name when it is displayed OK for all the other columns in the table. Open another table with the same schema, and it shows there.
Meanwhile in the other table...
the last I heard was that HimanshuS-msft wanted the table schema, which I dumped in this thread as plain text (since we can't upload any type of file other than pixs). And this is just a minor UI display glitch, so not losing any sleep over it. Just doing my part to help improve the product and keep MS on its toes, as it were. 😉
12 Replies
Hi Element115
Thanks for using Fabric Community.
I have tried checking the schema for the tables present in lakehouse. I couldnt find any column without a datatype. Hence this is not a bug.
Delayed Refresh: If you recently modified the schema, there might be a delay before Fabric updates the visual display. Try refreshing the table view or the entire Lakehouse interface.Caching: Clear your browser cache or try a different browser to rule out caching issues that might prevent the updated schema from displaying.
Column Width: Experiment resizing the column to see if the data type appears as the column widens. It might be hidden due to space restrictions.
Browser/Zoom Issues: Ensure your browser zoom is at 100% and that there are no browser extensions or display settings that could be obstructing the data type's visibility.
UI Glitch: Close and reopen the table or try reloading the entire Fabric page. Sometimes temporary UI glitches can cause quirks in the display.
Hope this helps.
Are you not able to see the datatype when you expand the table also?I didn't check the tree hierarchy at the time... was busy doing my work and writing up various 'bug' reports for Microsoft 😉 It's not like it bothers me, but I thought it's one thing Microsoft should be aware of so they could eventually fix it so that the UI behaves the way all users are used to see a UI behave.
FYI the column resize does not work for lakehouse table UI. And I was told that's also not a bug. 😉
Hi Element115
We haven’t heard from you on the last response and was just checking back to see if you got some insights regarding your query. Otherwise, will respond back with the more details and we will try to help.
Thanks
Element115 : I am in agreement with Anonymous on this at this time it does not look to be bug . But still I want to check the schema for both the tables . Can you please share schema details . I did tried different options of the data type and all of them works just fine .
Thanks
HimanshuOk here's the table schema in xslx ... bloody hell! how do you upload a file on here??
I got a 23x23 table! Can't even use the Table widget in this editor.
This is the best I can do until you provide an link for file upload:
TABLE_CATALOG TABLE_SCHEMA TABLE_NAME COLUMN_NAME ORDINAL_POSITION COLUMN_DEFAULT IS_NULLABLE DATA_TYPE CHARACTER_MAXIMUM_LENGTH CHARACTER_OCTET_LENGTH NUMERIC_PRECISION NUMERIC_PRECISION_RADIX NUMERIC_SCALE DATETIME_PRECISION CHARACTER_SET_CATALOG CHARACTER_SET_SCHEMA CHARACTER_SET_NAME COLLATION_CATALOG COLLATION_SCHEMA COLLATION_NAME DOMAIN_CATALOG DOMAIN_SCHEMA DOMAIN_NAME 1 LH_RWS dbo FACT_RWS_15M DATE 1 null YES date null null null null null 0 null null null null null null null null null 2 LH_RWS dbo FACT_RWS_15M M15 2 null YES datetime2 null null null null null 6 null null null null null null null null null 3 LH_RWS dbo FACT_RWS_15M HOUR 3 null YES datetime2 null null null null null 6 null null null null null null null null null 4 LH_RWS dbo FACT_RWS_15M DATETIME 4 null YES datetime2 null null null null null 6 null null null null null null null null null 5 LH_RWS dbo FACT_RWS_15M ID_RWS 5 null YES varchar 8000 8000 null null null null null null utf8 null null Latin1_General_100_BIN2_UTF8 null null null 6 LH_RWS dbo FACT_RWS_15M AIR_TEMP 6 null YES float null null 53 2 null null null null null null null null null null null 7 LH_RWS dbo FACT_RWS_15M PRECIPITATION 7 null YES float null null 53 2 null null null null null null null null null null null 8 LH_RWS dbo FACT_RWS_15M ATMOSPHERIC_PRESSURE 8 null YES bigint null null 19 10 0 null null null null null null null null null null 9 LH_RWS dbo FACT_RWS_15M BATTERY_STATUS 9 null YES bigint null null 19 10 0 null null null null null null null null null null 10 LH_RWS dbo FACT_RWS_15M PAVEMENT_CHEMICAL_CONCENTRATION 10 null YES bigint null null 19 10 0 null null null null null null null null null null 11 LH_RWS dbo FACT_RWS_15M PAVEMENT_TEMP 11 null YES float null null 53 2 null null null null null null null null null null null 12 LH_RWS dbo FACT_RWS_15M PAVEMENT_BLOCK 12 null YES bigint null null 19 10 0 null null null null null null null null null null 13 LH_RWS dbo FACT_RWS_15M PRECIPITATION_RATE 13 null YES float null null 53 2 null null null null null null null null null null null 14 LH_RWS dbo FACT_RWS_15M PRECIPITATION_SITUATION 14 null YES bigint null null 19 10 0 null null null null null null null null null null 15 LH_RWS dbo FACT_RWS_15M RELATIVE_HUMIDITY 15 null YES float null null 53 2 null null null null null null null null null null null 16 LH_RWS dbo FACT_RWS_15M SOLAR_RADIATION 16 null YES bigint null null 19 10 0 null null null null null null null null null null 17 LH_RWS dbo FACT_RWS_15M SURFACE_DEPTH 17 null YES float null null 53 2 null null null null null null null null null null null 18 LH_RWS dbo FACT_RWS_15M SURFACE_FREEZE_POINT 18 null YES float null null 53 2 null null null null null null null null null null null 19 LH_RWS dbo FACT_RWS_15M VISIBILITY 19 null YES bigint null null 19 10 0 null null null null null null null null null null 20 LH_RWS dbo FACT_RWS_15M WIND_GUST_DIRECTION 20 null YES bigint null null 19 10 0 null null null null null null null null null null 21 LH_RWS dbo FACT_RWS_15M WIND_GUST_SPEED 21 null YES bigint null null 19 10 0 null null null null null null null null null null 22 LH_RWS dbo FACT_RWS_15M Index 22 null YES bigint null null 19 10 0 null null null null null null null null null null
