Why imported table from onelake is black?

[jaryszek]

Hello,

I added new table from Data LakeHouse into my remote semantic model on top of that (direct lake, no sql endpoint) using XMLA endpoint in tabular editor 3 and my table became black:

Why this is happening. 

And additional question, in which premium version of tabular editor i will have this option? 

Best,
Jacek

[v-echaithra]

Hi @jaryszek ,

I hope the information provided is helpful. I wanted to check whether you were able to resolve the issue with the provided solutions. Please let us know if you need any further assistance.

Thank you.

[Nasif_Azam]

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

[jaryszek]

Hmm but after weekend i see taht table turned to blue:

Why ?
Maybeafter some refresh? 

Best,
Jacek

[v-echaithra]

Hi @jaryszek ,

The blue color means the table has been processed and data has been loaded successfully. So, it's no longer in the "unprocessed" state. This could have happened after the table underwent a full refresh or process.

You might have initiated a refresh, either through the Tabular Editor or the Lakehouse model itself. Once the refresh completed, the table's status changed to blue, indicating it was successfully processed and data is now available.

Thank you.

[Ahmed-Elfeel · Accepted solution]

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.

[jaryszek]

thank you, 

I didnt find option to "process table".
What i have is:

I did the step for full refresh, clicked save and...nothing change in remote semantic model:

(i hit refresh also in lakehouse semantic model).

Best,
Jacek

[Jai-Rathinavel]

@jaryszek Did you add any calculated column on the black table ? If you have added it then your table would fall back to direct query.

Thanks,

Jai 

[jaryszek]

You can not add column in onelake mode. It will only work with SQL endpoint flavour I suppose.