Maybe SQL Editor resolves column names in a different way compared to regular notebook. Anyway, if I were you I would check first how this attribute was defined in Snowflake.

If it was defined using unquoted identifier, like below

CREATE TABLE employee(employeeid INT)

 Then this attribute will be stored and resolved in uppercase. 

If your table attribute was defined using double-quoted identifier then it will preserve case-sensitivity, as you can see in following example from Snowflake documentation.

Now, if it was defined using double-quoted identifier then you have to use double quote as they suggest in databricks documentation, otherwise it won't work.