☑ cool new feature
☑ could help many users!
☑ removes something that feels like a „bug“
☐ nice to have
☐ nobody needs it
What inspired this wish list request?
Working with multiple open data tables in JMP often creates implicit dependencies (e.g., linked Summary and Subset tables). In the GUI, the “view associated data” icon reveals these relationships, but there is no equivalent JSL functionality. [TS-00278736]This makes it difficult to safely close tables or manage temporary analysis outputs.
Working with multiple open data tables in JMP often creates implicit dependencies (e.g., linked Summary and Subset tables). In the GUI, the “view associated data” icon reveals these relationships, but there is no equivalent JSL functionality. [TS-00278736]This makes it difficult to safely close tables or manage temporary analysis outputs.
What is the improvement you would like to see?
I would like a complete JSL API to query and manage dependencies between open data tables and their associated reports. Ideally, this would include:
I would like a complete JSL API to query and manage dependencies between open data tables and their associated reports. Ideally, this would include:
dt << GetMainTable();to return the parent data table.dt << GetDependentTables();to return all child tables derived from it.dt << HasUnsavedReports();anddt << GetAssociatedReports();to detect report windows not saved as table scripts.- A global function such as
GetOpenTableDependencyGraph();returning the full dependency graph of all open tables.
These APIs should expose the same dependency information that JMP already shows in the Windows List.
Why is this idea important?
Scripted workflows need reliable ways to prevent accidental loss of dependent tables or reports when closing a parent table. A JSL‑level dependency graph would improve robustness, automate cleanup procedures, and allow consistent management of derived tables. It would also align scripting capabilities with the GUI, making automated processes safer, clearer, and easier to maintain.
other wishes from
Scripted workflows need reliable ways to prevent accidental loss of dependent tables or reports when closing a parent table. A JSL‑level dependency graph would improve robustness, automate cleanup procedures, and allow consistent management of derived tables. It would also align scripting capabilities with the GUI, making automated processes safer, clearer, and easier to maintain.
other wishes from
1 Comment