Advance your Data & AI career with 50 days of live learning, dataviz contests, hands-on challenges, study groups & certifications and more!
Get registeredGet Fabric Certified for FREE during Fabric Data Days. Don't miss your chance! Request now
today , with a scheduled dataflow , we receive an entity error in a #date function :
13/01/2021 07:31:01,xxxxFailed,X3_xxxxx,13/01/2021 07:31:33,13/01/2021 07:32:04,Failed,Error: The import #date matches no exports. Did you miss a module reference? Request ID: 6ab8d9ee-7609-42fa-82f1-6940d0eac881 Activity ID: 21a9b9bf-ce5a-4ce1-8d3c-8cecad28b74b
. This task works every day without errors :
we try to build a new test column
but with the same error
this is the function #date doc
do we miss something ?
Solved! Go to Solution.
Had the same problem today. It seems to be working on the Desktop, but not on Power BI Service.
@_paolo_m Maybe try inserting a string format and then convert it to Date as a workaround?
Response from MS support:
Product team has identified this to be a known issue as multiple customers are facing the same issue. They have taken this as consideration to fix this issue on Priority.
We have the same issue since yesterday! #date is not working anymore.
... we are still modifing all involved dataflows . things like this make me doubt the power bi product
MS Support fixed this issue today. I can confirm, it works now 🙂
thank you brappold
workaround :
Had the same problem today. It seems to be working on the Desktop, but not on Power BI Service.
@_paolo_m Maybe try inserting a string format and then convert it to Date as a workaround?
thank you so much , we start working now with the most important dataflow with your solution .
hope MS solve asap , i have tons of #date ....
Advance your Data & AI career with 50 days of live learning, contests, hands-on challenges, study groups & certifications and more!
Check out the October 2025 Power BI update to learn about new features.
| User | Count |
|---|---|
| 63 | |
| 18 | |
| 12 | |
| 11 | |
| 10 |