https://community.qlik.com/t5/Data-Movement-Streaming/Num-does-not-work-in-QS-when-source-is-Snowflake/m-p/2041039#M777 <P>When the source was Hana, the num(field) was working fine.</P> <P>For eg. Field A had a value 000000001.</P> <P>Num(000000001) gave the result as 1.</P> <P>However, when we replaced the source with snowflake, the num() is throwing null values.</P> <P>Can someone please help&nbsp;</P> Wed, 19 Mar 2025 23:06:21 GMT SataPani 2025-03-19T23:06:21Z https://community.qlik.com/t5/Data-Movement-Streaming/Num-does-not-work-in-QS-when-source-is-Snowflake/m-p/2041039#M777 <P>When the source was Hana, the num(field) was working fine.</P> <P>For eg. Field A had a value 000000001.</P> <P>Num(000000001) gave the result as 1.</P> <P>However, when we replaced the source with snowflake, the num() is throwing null values.</P> <P>Can someone please help&nbsp;</P> Wed, 19 Mar 2025 23:06:21 GMT https://community.qlik.com/t5/Data-Movement-Streaming/Num-does-not-work-in-QS-when-source-is-Snowflake/m-p/2041039#M777 SataPani 2025-03-19T23:06:21Z https://community.qlik.com/t5/Data-Movement-Streaming/Num-does-not-work-in-QS-when-source-is-Snowflake/m-p/2041043#M778 <P>Try num#(000000001) to force QS to interpret the value as a number. I'm guessing the value has arrived as a string in Qlik.</P> Wed, 22 Feb 2023 16:12:58 GMT https://community.qlik.com/t5/Data-Movement-Streaming/Num-does-not-work-in-QS-when-source-is-Snowflake/m-p/2041043#M778 henrikalmen 2023-02-22T16:12:58Z