Forum Discussion
Semantic Model Data Refreshed "Invalid Date"
I create a semantic model on top of a mirrored database, through API, in order to use Power BI with logical metadata instead of physical metadata of the direct lake.
All my tables in the semantic model appears with a warning because of "Invalid Date" in Data Refreshed
I noticed there is no refresh in direct lake history, so Refresh Data date is probably null, so the Invalid Date (I found some mentions here of a UI bug related to null date handled as invalid in UI.
If I create the semantic model manually I do not have this issue, but the refresh history has one row, so there is a date in refresh data
I do not really understand why there is a refresh after manual creation and no after api creation, anyway this looks like a cosmetic issue, using copilot and power bi with the semantic model is working fine. Is it something known ? any plan to solve the Invalid Date issue, or is it possible to trigger a refresh through API to workaround this ?
Thanks for your help
Hi amergey,
Thank you for posting your query in the Microsoft Fabric Community Forum.
The “Invalid Date” warning appears because API-created Direct Lake semantic models don’t automatically trigger an initial metadata refresh, unlike manual creation. This leaves the refresh history empty, causing the UI to display Invalid Date but it’s purely cosmetic and doesn’t affect data access, Copilot, or reporting. To fix it, simply trigger a full refresh via the Power BI REST API right after creation. This populates the history with a valid timestamp and removes the warnings.
Best regards,
Ganesh Singamshetty.
3 Replies
Hi amergey,
Thank you for posting your query in the Microsoft Fabric Community Forum.
The “Invalid Date” warning appears because API-created Direct Lake semantic models don’t automatically trigger an initial metadata refresh, unlike manual creation. This leaves the refresh history empty, causing the UI to display Invalid Date but it’s purely cosmetic and doesn’t affect data access, Copilot, or reporting. To fix it, simply trigger a full refresh via the Power BI REST API right after creation. This populates the history with a valid timestamp and removes the warnings.
Best regards,
Ganesh Singamshetty.Hello amergey,
We hope you're doing well. Could you please confirm whether your issue has been resolved or if you're still facing challenges? Your update will be valuable to the community and may assist others with similar concerns.
Thank you.
Hello amergey,
Hope everything’s going great with you. Just checking in has the issue been resolved or are you still running into problems? Sharing an update can really help others facing the same thing.
Thank you.