You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Using a CSV file with number columns as the source for a lookup task will import those columns as strings.
To Reproduce
Steps to reproduce the behavior:
Download these CSV files and save them to Dropbox (these files can also be found in Dropbox (Flex Research) > temporary > github-issues > flexiodata-flexio > 579
In the web app, go to Functions
Click New > Extract Function
Save the function
Select one of the CSV files from the above ZIP file as your lookup file
Select "company" and "stage" as your key fields
Select "tot_deals" and "tot_value" as your return columns
Save the function
Expected behavior
If you test this function in the app, it works, because the "stage" test value is a string. We would expect it to work in Excel of Google Sheets then as well. However, open Google Sheets and try to that function with the "stage" parameter as a number and it will return nothing.
Screenshots
Additional notes
There are likely multiple things going on here -- 1) the lookup import was done pretty quickly and should probably do better type checking so that the columns are typed better. 2) The function execution should probably be a little more forgiving on type matches or something. Dunno -- maybe, maybe not.
The text was updated successfully, but these errors were encountered:
Describe the bug
Using a CSV file with number columns as the source for a lookup task will import those columns as strings.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
If you test this function in the app, it works, because the "stage" test value is a string. We would expect it to work in Excel of Google Sheets then as well. However, open Google Sheets and try to that function with the "stage" parameter as a number and it will return nothing.
Screenshots
Additional notes
There are likely multiple things going on here -- 1) the lookup import was done pretty quickly and should probably do better type checking so that the columns are typed better. 2) The function execution should probably be a little more forgiving on type matches or something. Dunno -- maybe, maybe not.
The text was updated successfully, but these errors were encountered: