This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. We're covering it all. You won't want to miss it.
Learn moreDid you hear? There's a new SQL AI Developer certification (DP-800). Start preparing now and be one of the first to get certified. Register now
Power BI is unexpectedly and erroneously forcing a CAST operation on specific numeric keys (NUMBER(19,0) / Whole Number), converting them to BIGINT within the generated SQL sent to Snowflake.
We have already opeend a support ticket on this. Below is the contents of that ticket.
Summary:
We initially connected over a Teams meeting and discussed your use of Snowflake as a data source, which you connected to Power BI Desktop via the Snowflake connector.
Power BI is applying a CAST operation on specific numeric keys (NUMBER(19,0) / Whole Number), converting them to BIGINT within the generated SQL sent to Snowflake.
You have three columns: "CARRIER_KEY_BIGINT," "CARRIER_KEY_NUM19," and "CARRIER_KEY_VARCHAR." The data type for "CARRIER_KEY_BIGINT" and "CARRIER_KEY_NUM19" is set to "Whole number," while "CARRIER_KEY_VARCHAR" is set to "Text."
When a 19-digit number is entered in each column, the "CARRIER_KEY_VARCHAR" column displays the data correctly, but the "CARRIER_KEY_BIGINT" and "CARRIER_KEY_NUM19" columns round off the last three digits.
We reproduced the issue on our end by pulling data from SSMS (Data source), and when the data type is "Whole number," the last three digits are also rounded off.
Our Engineering team has confirmed that this is expected behavior.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.