What inspired this wish list request?
I use a data table that pulls a rolling two years worth of data. Every morning when the report is run, some data points "expire" and some new data points are added based on the previous day's data. When that happens, all data points change what row they are on. Since row number is not important for any reports or graphs that I use, this makes no impact. BUT when putting into a JMP live control chart, this table is no longer able to be used because the triage function relies on a static row number for each point in order to tie triage history to that specific data point.
What is the improvement you would like to see?
Currently JMP live triaging identifies points based on row number. If the row number changes when data is refreshed (for rolling data tables or in instances where rows are deleted or inserted in the middle), then all triaging is lost. When the data is refreshed in these instances, JMP re-alarms all points out of control and removes any past history of what was done on triaged points.
I would like JMP live to allow for an ID column or something similar to use as a unique identifier to tie the triage history to. The control chart ideally will look the same and will interact the same, but triage will have a more stable way to connect specific data points to their triage history. If no ID column is selected, then it can default back to row number
Why is this idea important?
This would significantly increase the usefulness of the triage function in JMP live which has been heavily touted as one of the large advantages of using JMP live over local desktop JMP. JMP live needs the flexibility to allow a data table to change without erasing all past history.