このウィッシュリストリクエストのきっかけは何ですか?
What I want to see improved is an issue with imported data when updating from JMP14 to JMP18 (some data becomes null).
Specifically, place test data in c\temp, run scripts Source14a and Source14b in JMP14 and JMP18, and compare. Unlike JMP14, in JMP18, when importing data that contains a mixture of YYYY/MM/DD type and YYYY/MM/DD H/MM/SS type in one column, some of the data will be converted to null data.
改善してほしいことは何ですか?
Revert the data import method to the same as JMP14, or add an option to revert to the same as JMP14.
Data that contains a mixture of YYYY/MM/DD type and YYYY/MM/DD H/MM/SS type often occurs in manufacturing sites. If this data becomes null, analysis cannot be performed, so it is important to be able to read it without generating nulls like in JMP14.
この考え方がなぜ重要なのでしょうか?
Customer support also suggested using the Source14aREV script, but it is difficult to change to the proposed script for two reasons. 1) There are already hundreds of scripts running, and it is difficult to change all of them without making mistakes. 2) Even when creating a new script, Source14a format scripts are easily created when opening a file in JMP14. It is very time-consuming for users to convert all date and time data columns in the read data to Source14aREV format (for example, one file contains more than 1,000 rows of date and time data columns).
Therefore, it is very important for the manufacturing industry to improve data reading as a function of JMP, rather than modifying the script.
Apart from this defect, JMP18 is a stable and excellent product. Please eliminate the inconvenience of reading data. If you do so, fewer users will require older JMP versions when renewing their licenses.