Forum Discussion
Super UserGraphQL Update Issue
Hi Pragati11 ,
1. GraphQL’s refresh process can sometimes be inconsistent with detecting column changes. While new objects such as tables or views are typically recognized immediately, updates to existing tables may not always be reflected right away. In such cases, it may be necessary to manually refresh GraphQL’s metadata by removing and re-adding the table or performing a full source refresh.
2. Pushing schema changes via Git updates the Fabric SQL database, but GraphQL maintains its own schema layer. Changes made through Git are not automatically communicated to GraphQL, so while it is not required to push changes to GraphQL via Git, you do need to refresh GraphQL to ensure the table structure is updated.
Thank you for your time, and I hope this is helpful.
I did try removing the table and adding it again to the GraphQL. It did bring in the new columns but then it deleted the relationships that this table had with few other tables.
So, for a workaround I tried bringing an additional table to GraphQL and refreshed the schema, it pulled the column updates for the table I made changes to.
So coming to my last question.
Do we have any ETA on if this will issue with the GraphQL metadata refresh will be fixed in future? 😊
Hi Pragati11 ,
Thank you for confirming and testing both approaches.
Yes, removing and re adding the table is a known way to refresh the column metadata in GraphQL.
Your workaround adding another table to trigger a broader schema refresh is clever and aligns with what other users have successfully tried.At this time, Microsoft has not announced a specific ETA for when GraphQL will fully support automatic column level schema updates without affecting relationships or requiring manual intervention.
Since this behavior can impact client environments, I recommend raising a support ticket with Microsoft Fabric or using the Send Feedback option directly from your workspace. This helps bring more visibility to the issue and may contribute to prioritizing a fix
How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn
Learn about Microsoft Fabric feedback - Microsoft Fabric | Microsoft Learn
Once you’ve reviewed this, please let us know which route you chose. It will help other users as well. Thanks.
Super UserThank you for your response.
I did Update the schema at data source level.
I have questions here:
- What do you mean by GraphQL not always picks up column level schema updates? Are there scenarios where these are updated?
- I am pushing a schema level change in the table from the database, therefore only pushing theae changes via Git. Why would I push GraphQL via Git? It should pick up automatically updates once the database schema is updated in workspace.
Community SupportHi Pragati11 ,
1. GraphQL’s refresh process can sometimes be inconsistent with detecting column changes. While new objects such as tables or views are typically recognized immediately, updates to existing tables may not always be reflected right away. In such cases, it may be necessary to manually refresh GraphQL’s metadata by removing and re-adding the table or performing a full source refresh.
2. Pushing schema changes via Git updates the Fabric SQL database, but GraphQL maintains its own schema layer. Changes made through Git are not automatically communicated to GraphQL, so while it is not required to push changes to GraphQL via Git, you do need to refresh GraphQL to ensure the table structure is updated.
Thank you for your time, and I hope this is helpful.
- Pragati11
I did try removing the table and adding it again to the GraphQL. It did bring in the new columns but then it deleted the relationships that this table had with few other tables.
So, for a workaround I tried bringing an additional table to GraphQL and refreshed the schema, it pulled the column updates for the table I made changes to.
So coming to my last question.
Do we have any ETA on if this will issue with the GraphQL metadata refresh will be fixed in future? 😊
- V-yubandi-msft
Hi Pragati11 ,
Thank you for confirming and testing both approaches.
Yes, removing and re adding the table is a known way to refresh the column metadata in GraphQL.
Your workaround adding another table to trigger a broader schema refresh is clever and aligns with what other users have successfully tried.At this time, Microsoft has not announced a specific ETA for when GraphQL will fully support automatic column level schema updates without affecting relationships or requiring manual intervention.
Since this behavior can impact client environments, I recommend raising a support ticket with Microsoft Fabric or using the Send Feedback option directly from your workspace. This helps bring more visibility to the issue and may contribute to prioritizing a fix
How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn
Learn about Microsoft Fabric feedback - Microsoft Fabric | Microsoft Learn
Once you’ve reviewed this, please let us know which route you chose. It will help other users as well. Thanks.- Pragati11
Hi V-yubandi-msft ,
I did ended up using my way of adding a table and removing it again to push hard schema refresh. As GraphQL has been announced to be in GA at Ignite recently, I will wait for Microsoft to come up with an ETA on this issue.
Thanks for your comments here. 🙂
I will accepting multiple solutions to this thread so it can help community members with the similar issue.