JMP18 Excel Save Behavior

[#1]

Hello Community! When saving a table of character columns as an xlsx Excel file, JMP18 adds some kind of invisible flag that makes Excel think it is has numbers stored as text. This is a different behavior than JMP17 and is causing data interpretation issues on downstream non-JMP scripts that use this Excel file. Any advice on how to work around this or change this behavior? I cannot change the columns that have numbers to Numeric since the top three rows that have strings need to be there. They must remain Character.

Left is JMP17 behavior (good), right is JMP18 behavior (bad). Both Excel files generated w/ same script.

JMP Table before saving

Thanks!

Mike

[#2]

There has been some changes with JMP18 regarding JMP and Excel  JMP Note 655981 - Changes to the import of Microsoft Excel files in JMP® 18  . And for the fix... I'm not really sure as I think what JMP is doing is basically correct (you have character column -> use characters) but that might not be that convenient with excel as it is a spreadsheet. You could maybe try saving your data as .csv and see if excel loads that "correctly"

[#3]

Thanks for the quick reply. I would like to keep the color coding in the file if possible but will give csv a shot to see if it helps in theory. We could certainly do some adjustments on the back end to accept these files with the new encoding but would prefer not to.

-Mike