Materialized Lake View - 'Invalid Date, Invalid Date'

Hi TheFifthJoin ,

Thank you for providing the details. Even reverting to a previous version may not fully resolve it, since cached metadata can persist across sessions and environments. anilgavhane , suggestions are still relevant and worth trying.
For the

"Private link check failed"

This is probably not directly related to the MLV issue, but may be impacted by the same OPDG update. This error often occurs if

1. The Fabric workspace or capacity isn’t properly registered in the Private DNS zone

2. The Private Link endpoint is misconfigured or not fully propagated

3. You’re using On Premises Data Gateway, which doesn’t fully support Private Link

If you’re in a secure VNet environment, you might consider using the VNet Data Gateway, as it’s designed for Private Link and can help avoid these errors.

Alternatively, you can

1. Disable redirection temporarily and test creating the MLV with a new name and explicit casting
2. Check Private DNS zone records to ensure Fabric endpoints are properly registered
3. If using OPDG with Private Link, try switching to VNet Data Gateway

Helpful Reference:
Solved: Seeking Advice: Private Link and VNet Data Gateway... - Microsoft Fabric Community

Thanks for prompt response anilgavhane .

Regards,
Yugandhar.

Hi V-yubandi-msft 

To update - bit of a mixed bag of solutions.. The rollback of the OPDG seemed to fix the columns going into strange orders when we added/removed a column from the materialized lake view. I've not seen this as a known issue, but rolling back seemed to resolve and we'll wait for a new update release before trying to update the OPDG again.

The 'Invalid Date, Invalid Date' seems to be being displayed when my date value in the raw data is NULL. If we load this via the sql endpoint in SSMS, the fields display as null values as expected.. a bit of an odd display, but I believe its just a display quirk, rather than an actual issue with the data. Hopefully this will get addressed in a future release also, but for now, ignoring it is doing no harm as the 'Invalid Date, Invalid Date' message doesnt pull into powerBI visualisation either.

Finally the Private link issue was a much wider issue that affected all of south-west connections. Something to do with an error in an update MS pushed - they address, rolled back internally, and the error disappeared.

Thanks for checking back!