Forum Discussion

Mauro89's avatar
Mauro89
Super User
8 months ago
Solved

Lakehouse schema change not updated in GraphQL API

Hi community,

 

I have updated my Lakehouse schema where a table was already in use in a GraphQL API item.

But the schema (and data change) was not reflected and updated automatically in my GraphQL API item.

 

Any ideas why? Or is it a known limitation as of now?

 

Thanks and best regards!

API for GraphQL

6 Replies

  • Ugk161610's avatar
    Ugk161610
    Super User
    8 months ago

    Hi Mauro89 ,

     

    We’ve seen the same thing in our workspaces, and right now GraphQL APIs in Fabric don’t automatically pick up schema changes from Lakehouse tables. Even if the table structure changes or new columns appear, the GraphQL item keeps using the schema it captured at the time the API was created. Because of that, the API won’t show new fields or updated types until you refresh it manually.

     

    In our case, the only way to get the new schema to show up was to open the GraphQL API item, let it reload the metadata, and then save it again. Sometimes we even had to remove the table from the API and add it back. Once we did that, both the structure and the updated data started showing correctly.

     

    So yes, this is a limitation at the moment — schema updates in the Lakehouse don’t sync automatically into GraphQL. Hopefully this becomes more dynamic in future updates, but for now, a manual refresh inside the GraphQL item is needed whenever the underlying table schema changes.

     

    If you want, I can outline the exact steps we followed to force the refresh.

    – Gopi Krishna

    • Mauro89's avatar
      Mauro89
      Super User
      8 months ago

      Hi Ugk161610,

       

      awesome to know and thanks for sharing!

      I did the same as you, reloading the tables to see the changes. 

      I will check the ideas section if this topic is already there, if not I will add it. 

      Thanks and best regards. 

      • Ugk161610's avatar
        Ugk161610
        Super User
        8 months ago

        Hi Mauro89 ,

         

        Glad to hear it worked on your side as well — sometimes the manual refresh is the only reliable way until the schema sync becomes smarter. And yes, adding this to the Ideas section would definitely help, because a lot of people would benefit from automatic updates in GraphQL when the Lakehouse schema changes.

         

        Thanks for checking, and feel free to update the thread if you find anything new.

        Best regards,
        Gopi Krishna