User Community
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 

  • JMP Security Notice: CVE-2026-109618 and CVE-2026-109619

    JMP promptly initiated a review of its products, services, and relevant infrastructure for exposure to CVE-2026-109618 and CVE-2026-109619.

    Our assessment of JMP products has not identified exposure to these vulnerabilities. Where remediation was required within supporting environments, appropriate security updates and controls have been applied and validated.

    We have identified no evidence of successful exploitation or unauthorized access to JMP systems or customer information associated with these vulnerabilities.

    JMP continues to monitor the issue and relevant vendor guidance. No action is required by JMP customers at this time.

  • Don’t miss your chance to experience Discovery Summit Europe at our best available rate! Early bird registration through 31 Oct.
  • Graph Builder Toolbar streamlines interactive graphing. Creates shortcuts on Report and GraphBuilder Helpers toolbars. Download and install the extension.

JMP Wish List

We want to hear your ideas for improving JMP. Share them here.
Choose Language Hide Translation Bar
0 Kudos

"Saving Script to Database"

Status: Archived Submitted by on ‎09-13-2018 01:15 PM
1 Comment (1 New)

If I have a .JMP data table, and do some analysis, I can "Save Script to Data Table", then save my data table. Then a future colleague who has my JMP data table can see what analyses I ran on the data.

 

But when data are coming from Query Builder, the master source for the data is on the database. My .JMP data table is no longer the source of record that a colleague is likely to find. Instead, they re-pull the data and lose sight of the fact that analyses were done on that data.

 

I'm not 100% sure what this looks like, but I think it would be helpful to somehow save a record of 'this data was once pulled into JMP and these scripts were useful when analyzing it' into the database. Some way of archiving the work that was done to be part of the database. Saving Script to Database is only part of it; you need to know what records in the database that script could apply to as well.

 

So although I don't have the full details I am putting the idea out there in the hopes that others might have some great ideas as to how we can build on it.

1 Comment
Ryan_Gilmore
Community Manager Community Manager
Community Manager
‎10-26-2022 04:34 PM
‎10-26-2022 04:34 PM
Status changed to: Archived
We are archiving this request. If this is still important please comment with additional details and we will reopen. Thank you!