BUG::DATETIME TYPE::VALUES OK IN DF BUT ALL NULL IN LAKEHOUSE

[Element115]

CONTEXT:

DFg2 uses M to generate this Dim table (DimTime):

As you can see, the following columns of type DATETIME contain the correct values: Hour, Quarter Hour, Next Hour, Next Quarter Hour, Hour Number (type NUMBER or INTEGER, BIGINT in LH), Period of Day (type TEXT).

These columns are explicitly converted to type DATETIME because of the limitation of lakehouse that do not handle the TIME data type. 

The DFg2 is then published to the LH:

ISSUE:

Everything was fine until today I open the LH SQL endpoint and take a look at DimTime table and find this:

As you can see, the columns now all (except Time and Hour columns even though they are of the same type!) show up as having null values, even the column of type TEXT!!! 

Just to reiterate:  After creating the DFg2 and testing it, so making sure it worked, the values in the LH for these columns were not null. 

Seriously guys, what on earth is going on here???

Here is the table schema:

[Element115]

This is getting more interesting by the minute!  As you can see, after I deleted the DimTime table from the LH, and tried to re-publish the DFg2, the Choose destination settings dialog has these very same columns unselected by default, even thought the data types of the datetime cols are the same types as the cols that are auto selected.

[Element115]

From the DFg2, when choosing the Data destination, we can see that these columns, although not null in the DF, have been nulled in the Data destination dialog, which is a new occurrence as, like I said before, it used to work fine before today:

[v-nikhilan-msft]

Hi @Element115 

Thanks for using Fabric Community.

Apologies for the issue you have been facing. For better understanding the issue I will request you to please go ahead with Microsoft support on this. 
https://support.fabric.microsoft.com/en-US/support/

After creating the ticket please provide the details here. This would help us in internal tracking.
Thanks

[Element115 · Accepted solution]

I deleted the dim table, re-published the DFg2 using New table instead of existing table (as I did the first time), and all columns showed up again as having non-null values in the LH.  Re-opened the DFg2 to change New table option to Existing table in Data destination.

So another one of these strange transient bugs.