SQL Endpoint not updating to semantic models

[RCrom]

Hi all,

We have an issue with the fabric end points. The main issue is that some tables do not show up in our semantic models. So we did some debugging. 

The table does show up in the Lakehouse. As shown below.

If we connect to the SQL Endpoint using SSMS, we see the table. As shown below.

If we open up the endpoint online ( web version) we cannot find this table. If I then open a SQL query in that same online web version endpoint and I select * from this table. I get the results i want. So no errors, no nothing. But in the left schema/table list the table is not there. This is not really an issue, however.... We can also not add this table to our semantic models.

The table does not show up, so we are guessing that the semantic model uses that same list where it doesn`t show up in. 

We tried refreshing the online SQL Endpoint, no succes. We have never had this issue untill this week. Has anyone encounterd a same issue? Or does anyone have a fix for this? Strange part is, some tables get added with no issue. And we have a few of them that will not work even if we wait for days.

Greetings. Thanks in advance.

[v-csrikanth]

Hi @RCrom 
Sorry for the late response.
Since the issue persists despite trying the usual troubleshooting steps, here are some advanced debugging steps you can have a try:

• Manually trigger a schema refresh by running:
  ********************************************************
  ALTER TABLE fct_backflush_transactions ADD DUMMY_COLUMN INT;
  ALTER TABLE fct_backflush_transactions DROP COLUMN DUMMY_COLUMN;
  ********************************************************
  This forces the system to re-register the table in Fabric.
• Manually drop & recreate the table:
  ********************************************************
  DROP TABLE IF EXISTS fct_backflush_transactions;
  CREATE TABLE fct_backflush_transactions (...) -- Define schema manually
  *******************************************************
• If using Import Mode, try switching to DirectQuery and check if the table appears.

If the above information is helpful, please give us Kudos and mark the response as Accepted as solution.

Best Regards,

Community Support Team _ C Srikanth.

[RCrom · Accepted solution]

Hi,

Thx for the response. 

About an hour ago the table`s appeard. It took nearly a week for the table`s to show up. Adding new tables is now instant, so i am guessing this was a microsoft issue in the backend.

Greetings.

[RCrom]

Hi! Thanks for the responds.

See my responses in Red:

• In Power BI Service, navigate to SQL analytics endpoint and click Refresh Metadata to force an update & wait a few minutes and check if the table appears in the semantic model. We tried this, no succes.
• Check schema & permissions of the table which belongs to the correct schema and fabric user role has SELECT permissions on the table. All our schema`s and tables have the same permisions, there is no difference.
• Unsupported data types (e.g., complex types like JSON, arrays, or geography) prevent tables from appearing in semantic models.
  Eg: Run SELECT * FROM INFORMATION_SCHEMA.COLUMNS WHERE TABLE_NAME = 'fct_backflush_transactions' to inspect column types. There is no unsported data types, its mainly Int`s, varchars, date`s of floats.
• Try recreating the table if does not appear & renaming the table. We tried this, no succes.
• Manually recreating the table under a different name (fct_backflush_transactions_v2) and refreshing the SQL Endpoint. Verify if any new versions available. We tried creating the table with a new name, but its also no success. 

A completly different table did work, that table uses the same data types. Same permisions etc.

Greetings.

[v-csrikanth]

Hi @RCrom 
Thanks for reaching out to Microsoft Fabric Community.

This issue where a table is visible in the Lakehouse and SQL Endpoint (SSMS) but not in the Power BI semantic model suggests a potential metadata synchronization or indexing issue within Fabric.
Here are some steps to troubleshoot and fix the issue:

• In Power BI Service, navigate to SQL analytics endpoint and click Refresh Metadata to force an update & wait a few minutes and check if the table appears in the semantic model.
• Check schema & permissions of the table which belongs to the correct schema and fabric user role has SELECT permissions on the table.
• Unsupported data types (e.g., complex types like JSON, arrays, or geography) prevent tables from appearing in semantic models.
  Eg: Run SELECT * FROM INFORMATION_SCHEMA.COLUMNS WHERE TABLE_NAME = 'fct_backflush_transactions' to inspect column types.
• Try recreating the table if does not appear & renaming the table.
• Manually recreating the table under a different name (fct_backflush_transactions_v2) and refreshing the SQL Endpoint. Verify if any new versions available.

If the above information is helpful, please give us Kudos and mark the response as Accepted as solution.

Best Regards,

Community Support Team _ C Srikanth.