Forum Discussion
Solution SageWrite DAX Query in Service Fails with Power Query Function Generated Table
Hi Martin_D,
Thanks for getting back and sharing the update. I understand that the issue persists in Power BI Service but not in Power BI Desktop. Since this might be a potential bug, we recommend raising a Microsoft support ticket for further investigation.
In my previous response, I shared the link how to create a support ticket. If you haven’t already, please raise a support ticket:
Create a Microsoft Support TicketOnce you've raised the ticket, please share any updates in the community. This will assist others who might be experiencing the same issue. If this is helpful, kindly accept it as a solution and leave a "Kudos".
Community SupportHi Martin_D,
Thanks for posting your query in microsoft fabric community forum.
Since this is a data model circular dependency issue on your side, I notice there are many columns, making it challenging to identify the root cause. Similarly, you can use Power BI Desktop DAX Query Editor.
If this helps then please Accept it as a solution and dropping a "Kudos" so other members can find it more easily.
Thank you.
Solution SageThank you, v-ssriganesh for looking into this.
This is exactly my concern: In Power BI Desktop query view it works. That's why I don't think it's a problem on my side. It must be some problem with Power BI service. But not all users that have build permission and want to query data in the web browser have privilege to download the file. And we also don't want grant this privilege to everyone. We need a solution that works in the web browser. We have this problem with many semantic models. That's just an isolation that I can share publicly.
Kind regards,
Martin
- v-ssriganesh
Hi Martin_D,
There are some considerations and limitation while using ‘Write DAX query feature’, Please refer this documentation and make sure you are meeting all the requirements.
https://learn.microsoft.com/en-us/power-bi/transform-model/dax-query-view#considerations-and-limitationsIf this helps then please Accept it as a solution and dropping a "Kudos" so other members can find it more easily.
Thank you.
- Martin_D
Hi v-ssriganesh ,
Thank you for sharing the constraints. Although there are interesting constraints regarding other planned activities, specifically Git integration, there is no limitation that applies to or explains my situation.
Kind regards,
Martin
- v-ssriganesh
Hi Martin_D,
The error "Circular query chain present" indicates that your dataset contains a reference loop, specifically involving the fnCreateDateTable function. This issue arises when a query references another table that, in turn, depends on it, creating a cycle.
To resolve this, you should ensure that fnCreateDateTable does not depend on any tables that reference it. If you're using a dataset to determine the date range, you might want to consider using static parameters instead. This approach can help break the cycle and prevent the reference loop.
If this helps then please Accept it as a solution and dropping a "Kudos" so other members can find it more easily.
Thank you.