Forum Discussion
GraphQL update... mutation for Fabric SQL DB failing
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
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
- msturzen9 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- v-achippa9 days ago
Community Support
Hi msturzen,
Thank you for the clarification. You are correct that the stored procedure is only a workaround and does not resolve the original issue.
- Based on the repro you provided, the updateproduct mutation is failing with an InternalServerError, while the corresponding sql update works successfully. Since update mutations are supported for fabric sql databases, this behaviour is not expected.
I recommend please raise a Microsoft support ticket and provide all the required details including the request/operation details for one of the failed requests.
Create a Fabric and Power BI Support Ticket - Power BI | Microsoft Learn
Thanks and regards,
Anjan Kumar Chippa