JMP17 Upgrade Forcing Superscript Broke JMP14 Working Script

[#1]

Hi Folk, I would give an example of script but after troubleshooting an explanation should suffice.

I have a data table from a CSV source that has many columns of trace data that has a column name with units at the end. For degrees C the header is Temperature [0c] and for cubic meters per hour it is Air Flow [m3/h]. There are others. I built a script that opens this data file and another that has calculated limits that is static. Worked great in JMP14. Was forced into JMP17 which is fine; however, JMP17 is superscripting the C for Celsius and 3 for Cubic. My reference limit file does not have that, and when I iterate through the columns for plotting they do not match. The easy fix was to make the static reference files saved with superscript. However, that is not how the input data comes and I  fear some other future upgrade or use of the JMP data into some other user interface like PBI or SSRS will balk at it. 

Is there an easy fix for preventing this in JMP17? Or should I just stay happy that I have a short (or maybe Long) term fix.

[#2]

I am not sure why your column names are showing up with superscripts. On my side, I had no issues importing the attached csv file using the normal method of File -> Open with Preview. 

By the way, if you are using JSL scripting already, you may be interested in referencing columns by number instead of name. Here's an example from the Scripting Index entry for the Column function: 

Names Default To Here( 1 );
Open( "$SAMPLE_DATA/Big Class.jmp" );
col4 = Column( 4 );
ht = Column( "height" );
col4[1] + ht[2];

Notice that you can reference a column as "Column( 4 )" or "Column( "height" ); both are ok. This gets rid of any reliance on exactly matching the column names. This is a good fix if your data table is always formatted the same way (same number and order of columns). 

[#3]

---

@MikeTV99 wrote:

Hi Folk, I would give an example of script but after troubleshooting an explanation should suffice.

---

Providing a file or script that causes the issue is a great help!
It is more efficient to upload a file that can be used to reproduce the issue than to write a hundred words or more.

A guess: a "parse" error within a script

Open(
	"$DOWNLOADS/Superscript_Issue.csv",
	Import Settings(
		End Of Field( Other( ";" ), CSV( 0 ) ),
	)
);

column name = column(1) << get name;

Parse(column name)