Forum Discussion
Why imported table from onelake is black?
- 1 year ago
Hi jaryszek,
The black table color in Tabular Editor indicates that the table is in an unprocessed state this is a common occurrence when you add new tables to a semantic model through the XMLA endpoint
When you add a new table via XMLA:
- The table structure is created in the model metadata
- But the table hasn't been processed (data hasn't been loaded)
Tabular Editor shows unprocessed tables in black to visually distinguish them
For fixing this you need to process the table to load data from your Data LakeHouse:
Right click on the black table
Select Process Table
Choose processing options (usually "Process Full" for initial load)
Execute the processing operation
Or Use TMSL (Tabular Model Scripting Language):
{ "refresh": { "type": "full", "objects": [ { "database": "YourDatabaseName", "table": "YourBlackTableName" } ] } }if this post helps, then I would appreciate a thumbs up and mark it as the solution to help the other members find it more quickly.
Hey jaryszek ,
The reason your imported table from OneLake shows up in black in Tabular Editor 3 is because it’s a calculation group/table that comes from an external Direct Lake source, and not a standard imported/structured table. In Direct Lake mode, these objects appear in black to indicate that they are read-only, external references. You cannot modify their schema directly in the semantic model and they are controlled by the underlying Lakehouse.
Regarding Tabular Editor licensing:n The ability to connect to XMLA endpoints and work with semantic models is already available in Tabular Editor 3 (any edition). However, Tabular Editor 3 Desktop (free) does not include advanced productivity features.
Summary:
Black table = external Direct Lake source (read-only).
To transform, do it upstream or with calculated tables.
XMLA connectivity is available in TE3, but advanced features require Professional/Enterprise license.
Best Regards,
Nasif Azam