Forum Discussion
LakeHouse Models - Has this changed?
Potpot Everyone is new to Fabric. I would say that you found a creative work-a-round. Technically the documentation is correct as well as incorrect as the table is in the lakehouse (albeit via a shortcut). What you can't do is add a table to the semantic model that is not in the same, originally associated, lakehouse as there is no way to navigate to another lakelhouse when adding a table to the semantic model, only the tables (including shortcuts) within the associated lakehouse appear.
Thanks! I'm loving the platform but it does need some polish.
Any thoughts on the date time relationship? I'm using caution when building out some of my early solutions as I don't want to get caught relying on something that will later change or break!
In general a relationship based on datetime is undesirable due to the inherently high cardinality. Usual recommendation is to break it up into separate date and time dimensions.
Originally I planned to use straight date fields but found (perhaps a bug) that any date fields when loaded into a LakeHouse table would become a datetime field. To fix I made all dates into datetimes with 12:00am as the time.
yes, to make it even more confusing - There is not actually a "date" or "time" column type in DAX/VertiPaq. Behind the scenes everything is always datetime. The "date" values are datetimes pegged at 12:00:00am.
The cardinality issue still holds true though.
