☐ cool new feature
☑ could help many users!
☑ feels like a „bug“
☐ nice to have
☐ nobody needs it
Short:
Remove this "bug":
![hogi_0-1718655247423.png hogi_0-1718655247423.png](https://community.jmp.com/t5/image/serverpage/image-id/65300iBE3E53355DBBF276/image-size/medium?v=v2&px=400)
... and this one:
![hogi_1-1718655349163.png hogi_1-1718655349163.png](https://community.jmp.com/t5/image/serverpage/image-id/65301iBDD301F389C28D6B/image-size/medium?v=v2&px=400)
Long:
What inspired this wish list request?
If reports are open, Jmp is not able to sort a data table:
https://community.jmp.com/t5/Discussions/How-to-update-table-after-sorting/m-p/659014/highlight/true...
Same issue for data tables with linked subsets: sorting and concatenating data to the data table doesn't work.
Similar issue if a user wants to add rows to a data table .
linked subset:
sort → no
add rows → no
concatenate → no
open report:
sort → no
add rows → yes
concatenate → yes
What is the improvement you would like to see?
Please remove the restrictions.
e.g. "cut the link", like it's done for linked summary tables:
sort → no [why does SORT not "cut the link"?!?]
add rows → yes²
concatenate → yes²
² JMP automatically cuts the link:
![hogi_0-1725179686639.png hogi_0-1725179686639.png](/t5/image/serverpage/image-id/67771iB790C3EE7D521886/image-size/medium?v=v2&px=400)
Why is this idea important?
It's very likely that a user opened a linked subset, a linked summary table or a report before he tries to sort a table or add new rows.
Therefore, JMP users face this issue very often.
more wishes by![hogi_0-1707931852530.png hogi_0-1707931852530.png](https://community.jmp.com/t5/image/serverpage/image-id/61127iE949062BA5554263/image-dimensions/55x58?v=v2)