Forum Discussion
Random Error Being Thrown
I am unsure of how I could of fixed on the model that was originally referenced in this question. What I did after experiencing this problem and not having any luck with the adivice I was given was try to use one of my compay's already existing datasets with similar data. This went well until I started getting thrown errors again, this time when I uploaded my data to Service. If you check my profile you'll see another post that occurred about a week after this one about this. So I followed the advice that was given in that post and deleted the data that was originally in the data set so that I could switch to Import storage and the reupload the data that had to be deleted. I wasn't too sure whther this would work since the date data table and many others that were giving me problems from when I posted this post would have to uploaded again, but it did. I know this likely won't help many situations, but if you're in a similar situation don't be afraid to save what you have and work on a copy of your work or restart and try different storage modes to see if your issue persists. Also, don't be afraid to post on here often. Everyone is so hknowledgable, helpful, and willing to look your way.
Hi Anonymous,
Thanks for reaching out to the Microsoft fabric community forum and for the detailed breakdown. It seemd the root cause is related to how the date filter interacts with the DirectQuery model and possibly the date table’s relationships or transformations. As burakkaragoz have already responded to your query with trouble-shooting steps, kindly go through them and check if your issue gets resolved.
Apart from the mentioned steps, also go through:
* Try creating a duplicate of your current date table and use that in your visual or as a disconnected slicer to see if the problem persists. If the error disappears, the issue could be with the relationship or calculated columns in your original date table. This tests if the issue lies specifically within the date table logic or relationship.
* Check for Auto-Date/Time in Power BI Settings. In Power BI Desktop, go to Options -> Data Load, and disable the "Auto Date/Time" option. It sometimes causes hidden relationships and conflicts in DirectQuery models, especially when date fields are reused in multiple visuals. This setting is usually overlooked and can cause unexpected filtering behaviors in DirectQuery.
If none of the above help, at this point it may be worth opening a support ticket with Microsoft. Since it's tied to DirectQuery evaluation and only breaks on date filtering, they might be able to capture backend traces that aren't visible through the UI.
Please refer below link on how to raise a contact support or support ticket.
How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn
I would also take a moment to thank burakkaragoz, for actively participating in the community forum and for the solutions you’ve been sharing in the community forum. Your contributions make a real difference.
If I misunderstand your needs or you still have problems on it, please feel free to let us know.
Best Regards,
Hammad.
Community Support Team
If this post helps then please mark it as a solution, so that other members find it more quickly.
Thank you.
Hi Anonymous,
As we haven’t heard back from you, so just following up to our previous message. I'd like to confirm if you've successfully resolved this issue or were you able to raise a support ticket with Microsoft Fabric Support?
If yes, you are welcome to share your workaround and mark it as a solution so that other users can benefit as well. If you find a reply particularly helpful to you, you can also mark it as a solution.
If so, it would be really helpful for the community if you could mark the answer that helped you the most. If you're still looking for guidance, feel free to give us an update, we’re here for you!
So sorry, I ended up having to go a complete different direction and start from a prior model. My issue is resolved though, thank you for your help.
Hi Anonymous,
I'm glad that your issue has been resolved. Can you please mark the helpful reply as solution or provide the workaround which helped you in resolving the issue as a comment and mark it as solution so that the other community members facing similar issues will find the solution quickly.
Best Regards,
Hammad.