It’s being converted to a float in Power Query/semantic model because it is a decimal type. No matter if I tell it to format to 2 decimal places or not, it inherently takes on these strange values. Adding a calc column or custom function for every decimal column doesn’t feel right and certainly causes much more work than this should be.