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
Hey, just trying to do a really simple thing and write a 13 digit numeric string and store it as text. Don't want scientific notation. This gem doesn't accept the standard Excel behavior for this. If I type a single quote, and then a 13 digit number into an Excel cell, that signals to Excel to store the number as text. This gem stores the number as text, but it keeps the single quote. That's not correct, and it's counterintuitive behavior.
If I type an equals sign into Excel, then a double quote, then a 13 digit number, then another double quote, that signals to Excel to store the number as text. This gem stores it as scientific notation. That's not correct behavior.
What exactly is it I need to do to store a number so that it's not converted to a float with .0 on the end when I read it?
The text was updated successfully, but these errors were encountered:
I think you can enforce this by specifying the datatype for the exact cell you want with the types params which expects an array of various types float, string, boolean, nil should auto format it.
Hey, just trying to do a really simple thing and write a 13 digit numeric string and store it as text. Don't want scientific notation. This gem doesn't accept the standard Excel behavior for this. If I type a single quote, and then a 13 digit number into an Excel cell, that signals to Excel to store the number as text. This gem stores the number as text, but it keeps the single quote. That's not correct, and it's counterintuitive behavior.
If I type an equals sign into Excel, then a double quote, then a 13 digit number, then another double quote, that signals to Excel to store the number as text. This gem stores it as scientific notation. That's not correct behavior.
What exactly is it I need to do to store a number so that it's not converted to a float with .0 on the end when I read it?
The text was updated successfully, but these errors were encountered: