Forum Discussion
GraphQL update... mutation for Fabric SQL DB failing
Hi msturzen,
Thank you for reaching out to Microsoft Fabric Community.
Thank you ipkus for the prompt response.
As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided by the user for the issue worked? or let us know if you need any further assistance.
Thanks and regards,
Anjan Kumar Chippa
- msturzen14 days agoFrequent Visitor
Dear v-achippa,
to me there is no solution yet. All I have is a workaround for something - update of a single row in a SQL DB - that should just work out of the box. Don't get me wrong: I am thankful for the workaround.
At least - if there is some known product limitation - that should be documented in Fabric's GraphQL API documentation
Thanks
Martin- v-achippa10 days ago
Community Support
Hi msturzen,
Thank you for the clarification. Glad to hear that the issue is resolved now. We appreciate you sharing your feedback regarding the documentation and the workaround.
Thanks and regards,
Anjan Kumar Chippa- msturzen10 days agoFrequent Visitor
Hi v-achippa,
sorry if I come over as nitty-picky: My previous reply started with "... there is no solution ..."
I don't understand how you come to the conclusion the issue is resolved. To me this looks like a flaw/bug/defect/issue in Fabric's GraphQL implementation.
I think I provided minimal code samples to be able to reproduce the behaviour or point me at something I did wrong.
Looking forward to hear back from you.Best
Martin