JMP Knowledge Base

Latest Posts

• The Rename Directory() function might fail to rename directories on network drives

  Using the Rename Directory() function to change the name of a file system directory might return 0 when you attempt to rename a directory that is found on a network drive. To work around the issue, use the Move Directory() function, which can work for both local and network drives.  Here is an example: rc1 = Move Directory( "$TEMP/Loss Function Templates", "$TEMP/subB" );     [Previously JMP Note ...

  Wendy_Murphrey

  JMP Knowledge Base |

  Jan 10, 2023 11:48 AM

  222 views | 0 replies

• Using a JMP® script to delete a non-existent table property now returns error: cannot find table property

  Attempting to delete a table property that does not exist in a data table returns the error "cannot find table property." Because this is an error condition, the JSL script stops executing.  Prior versions of JMP® ignored the condition and proceeded with the next JSL statement. As a workaround, the Try() function can be used to escape the error condition and optionally execute a catch expression (...

  Wendy_Murphrey

  JMP Knowledge Base |

  Jan 10, 2023 11:45 AM

  228 views | 0 replies

• Using lists in JSL to perform the same task on multiple objects

  Overview Sometimes it is necessary to perform the same task on several objects of the same type. One approach is to repeat the statement for each object. However, this requires you to retype the statement for each object or use a loop. A handy approach is to send the message to a list of objects. This method requires you to type the message only once. Two examples are given below.   Example 1 Supp...

  Ryan_Gilmore

  JMP Knowledge Base |

  Jan 10, 2023 11:40 AM

  724 views | 0 replies

• Scripts that create a modal New Window might result in an error: Deleted Object Reference

  DisplayBoxes in a New Window that uses the <<Modal option are no longer accessible after the window is closed.  When a New Window is closed, the DisplayBoxes that make up the contents of the window are destroyed.  Earlier versions of JMP on Windows operating systems incorrectly allowed scripts to access the DisplayBoxes due to a delay in the actual destruction of the objects.   There are several w...

  Wendy_Murphrey

  JMP Knowledge Base |

  Jan 10, 2023 10:41 AM

  491 views | 0 replies

• SAS® data set created by submitting SAS code from JMP® leads to an invalid SAS variable name

  When JMP^® connects to SAS^®, the SAS VALIDVARNAME system option is set to ANY because JMP is more permissive with respect to column names. This can cause an error similar to the one below if the SAS code submitted from inside JMP creates a variable with a name that does not follow the default SAS variable name rules. ERROR: The value <variable name> is not a valid SAS name. To ensure that the SAS...

  Wendy_Murphrey

  JMP Knowledge Base |

  Jan 10, 2023 10:37 AM

  1172 views | 0 replies

• Missing values in SAS® datasets might be imported incorrectly

  When connecting to local SAS^® using a 64-bit version of JMP^®, the 64-bit SAS 9.4 IOM OLE DB provider used to import SAS datasets will import missing data with incorrect values. This problem is limited to importing data from local SAS using a 64-bit version of JMP where the 64-bit SAS 9.4 TS1M0 version of the SAS IOM OLE DB provider is installed. The recommended workaround for this issue is to inst...

  Wendy_Murphrey

  JMP Knowledge Base |

  Jan 10, 2023 10:30 AM

  805 views | 0 replies

• JMP® File Import does not find any files on Microsoft OneDrive®

  When importing files in JMP®, including Multiple File Import, JMP might not be able to see the file(s) in Microsoft OneDrive®.  This is due to how OneDrive represents the file(s) on some computers. To resolve this issue, please save the file to the local computer, including the Desktop or Documents.   Once saved to the local computer, JMP is able to see the file during the import process. If you c...

  Wendy_Murphrey

  JMP Knowledge Base |

  Jan 10, 2023 10:09 AM

  250 views | 0 replies

• JMP® date columns are exported as character data types through ODBC

  When exporting a JMP^® data table to a database using ODBC, JMP exports the data as either character (CHAR or NCHAR) or numeric (FLOAT or DOUBLE PRECISION) data types. If a column is defined as a JMP date or time, it exports as character data. Changing the data type to a proper date format would need to be handled by the receiving database.   [Previously JMP Note 46350]

  Wendy_Murphrey

  JMP Knowledge Base |

  Jan 10, 2023 10:07 AM

  206 views | 0 replies

• JMP® Clinical 7.1 Risk Based Monitoring report is missing cell coloring, and the Risk Indicator Selector

  In JMP^® Clinical 7.1 when running the Risk Based Monitoring report, the output might be incomplete. In the report the cells might not be colored, and/or the Risk Indicator selection outline could be missing. This issue is resolved in the JMP® Clinical 7.1.1 Hot Fix available here.     [Previously JMP Note 65319]

  laura_archer

  JMP Knowledge Base |

  Jan 6, 2023 12:31 PM

  234 views | 0 replies

• JMP® Clinical 7.1 Findings Time Trends: error for Lab Test Results equal zero

  There is a coding error in JMP^® Clinical 7.1 that sets a lab results with value 0 to missing. This issue is resolved with the Hot Fix available here.   [Previously JMP Note 64954]

  laura_archer

  JMP Knowledge Base |

  Jan 6, 2023 12:18 PM

  407 views | 0 replies

• JMP® Clinical 7.1 Exposure Summary: Inconsistency in calculation of total duration of exposure

  In JMP^® Clinical 7.1, the durations from Exposure Summary are calculated inconsistently. This issue is resolved in the Hot Fix  available here.   [Previously JMP Note 64956]

  laura_archer

  JMP Knowledge Base |

  Jan 6, 2023 12:17 PM

  300 views | 0 replies

• JMP® Clinical 7.1 API JSL results in an error when try to remove section

  In JMP^® Clinical 7.1 when trying to remove section using the JSL API, the following error can occur: The symbol "TabFilterReferenceList" is not defined in namespace "results" in
  access or evaluation of 'results:TabFilterReferenceList' , results:TabFilterReferenceList/*###*/ This issue is resolved by the Hot Fix available here.   [Previously JMP Note 64957]

  laura_archer

  JMP Knowledge Base |

  Jan 6, 2023 12:15 PM

  300 views | 0 replies

• JMP® Clinical 7.1 AE Narrative "ByNarrativeCategoryDetails" template not not populated diagnosis heading if MHCAT value for cancer history is missing

  The Adverse Event Narrative template "ByNarrativeCategoryDetails" has a section in the heading for "Diagnosis" that is populated when MHCAT=CANCER HISTORY. The Medical History section is populated with values when MHCAT=GENERAL MEDICAL HISTORY. The Hot Fix available here makes the requirement generic for cases when the narrative is run with a study that does not have these particular MHCAT values....

  laura_archer

  JMP Knowledge Base |

  Jan 6, 2023 12:13 PM

  369 views | 0 replies

• JMP® Clinical 7.1 Adverse Events Incidence screen can report a zero of infinite relative risk

  This hot fix makes an adjustment to the JMP Clinical 7.1 Adverse Event Incident Screen report. Results in the table are changed to
  apply a continuity correction (Gart and Nam 1988) to avoid infinity or zero as a Relative Risk value. The Hot Fix for this issue is available here.   [Previously JMP Note 65365]

  laura_archer

  JMP Knowledge Base |

  Jan 6, 2023 12:11 PM

  329 views | 0 replies

• JMP® Clinical 7.1 Adverse Event Report can show percentages greater than 100

  JMP^® Clinical 7.1 Adverse Event Report counts subjects multiple times in the Body System heading counts and percentages causing the values to be incorrect, and the percentages may exceed 100 percent. This issue is resolved in the Hot Fix available here.   [Previously JMP Note 65366]

  laura_archer

  JMP Knowledge Base |

  Jan 6, 2023 12:09 PM

  312 views | 0 replies

• JMP® Clinical 7.1 Adverse Event Report can incorrectly label columns with the wrong treatment group

  The output of the Adverse Event Report in JMP® Clinical 7.1 may be incorrect. The column headers indicating the treatment group may be incorrect, so that the counts and percentages are being attributed to an incorrect treatment group.   This issue is resolved in the JMP Clinical 7.1.1 Hot Fix. To resolve the problem apply the Hot Fix available here. 
      [Previously JMP Note 65320]

  laura_archer

  JMP Knowledge Base |

  Jan 6, 2023 12:07 PM

  274 views | 0 replies

• JMP® Clinical 7.1 Adverse Event Narrative templates do not split prior and con meds based on study day

  In JMP Clinical 7.1 there is not a standard way of splitting medications into prior treatment vs. on treatment. This hot fix standardizes this based on study day. The split is now based on study day and is calculated in loaddata to split prior and conmeds. The standardization uses the study day when available, and then either the first of the month if day is missing or the first of the year if mon...

  laura_archer

  JMP Knowledge Base |

  Jan 6, 2023 12:06 PM

  402 views | 0 replies

• JMP® Clinical 7.0: Mortality Time To Event Deaths that occur on study day one

  JMP® Clinical 7.0 and 7.1 removed deaths on study day 1 for Mortality Time to Event reports. JMP Clinical removes disposition records that occur on or before study day 1 to remove randomization and informed consent records. This means that a death on study day 1 will be removed. This issue is resolved in the Hot Fix available here.   [Previously JMP Note 64869]

  laura_archer

  JMP Knowledge Base |

  Jan 6, 2023 12:03 PM

  609 views | 0 replies

• JMP® Clinical 6.1 might exhibit slow performance when loading sample data

  This Hot Fix improves system efficiency to address performance issue in JMP® Clinical 6.1 when loading a study. To resolve the problem, apply the Hot Fix available here.   [Previously JMP Note 60234]

  laura_archer

  JMP Knowledge Base |

  Jan 6, 2023 12:01 PM

  388 views | 0 replies

• JMP® Clinical 6.1 hotfix to resolve issues with AE Narrative

  The Hot Fix available here resolves several issue with AE Narratives in JMP® Clinical 6.1. 1.  Enhancements so that AE Narrative can accommodate non-unique Findings test codes 2.  Resolved a bug that AE Narratives show incorrect information for USUBJID, medical history and findings 3.  There was a logic error that was preventing original units from working correctly This has been fixed 4.   Invest...

  laura_archer

  JMP Knowledge Base |

  Jan 6, 2023 11:59 AM

  271 views | 0 replies

• JMP® Clinical 6.1 Hotfix for Findings Reports

  The Hot Fix available here addresses a variety of issues with Findings Reports in JMP® Clinical 6.1   The first resolved issue is that Action Buttons are not enabled in Findings Distribution. This error occurs when running the following steps. 1) Run a Findings Distribution on data for LB domain
  2) Go to the Missing Test Details section of report
  3) Select subject counts in the summary table
  4) Notic...

  laura_archer

  JMP Knowledge Base |

  Jan 6, 2023 11:57 AM

  287 views | 0 replies

• JMP® Clinical 6.1 hotfix for Add Study issues

  The Hot Fix available here for JMP® Clinical 6.1 resolves four issues for Add Study.    1.  This Hot Fix allows JMP Clinical 6.1 to be compatible with SAS® 9.4 TS1M5, and allows studies to be added to JMP Clinical when SAS 9.4 TS1M5 is installed. This Hot Fix also resolves the following errors: 2.  The following error may also occur in JMP Clinical 6.1 when adding a study:  ERROR: The following do...

  laura_archer

  JMP Knowledge Base |

  Jan 6, 2023 11:55 AM

  262 views | 0 replies

• JMP® Clinical 6.1 Gives an Error Message when the Add Study Button is Clicked

  JMP^® Clinical 6.1 gives the following error when the Add Study button is clicked: The namespace addStudyDiag:addStudyOptions is not defined in access or evaluation of 'Expr:setParent', Expr:setParent/*###*/(addStudyDiag << getName)/*###*/ This error affects computers where the Regional Operating System (OS) and Language settings are set to a Language there the decimal separator is represented with...

  laura_archer

  JMP Knowledge Base |

  Jan 6, 2023 11:52 AM

  374 views | 0 replies

• JMP® Clinical 6.1 does not use supplemental domains by default

  JMP® Clinical 6.1 does not use supplemental domains, by default. To resolve the problem, apply the Hot Fix available here. For domain distribution reports at subject level the option to Merge Supplemental data is now on by default. This affects Distribution reports for the following domains:  AE, Events, Interventions, Findings and Study Visits.    [Previously JMP Note 60239]

  laura_archer

  JMP Knowledge Base |

  Jan 6, 2023 11:50 AM

  283 views | 0 replies

• JMP® Clinical 6.1 Adverse Event Narratives do not handle Supplemental Data

  This Hot Fix allows supplemental data to be used in Adverse Events Narratives in JMP® Clinical 6.1.  One option is to specify the full path and name to the input SAS data set containing supplemental data for AE narratives. This data set merges events using USUBJID and AESEQ. If AESEQ is not available in the original SDTM or ADAM data, AESEQ is defined after sorting events by USUBJID, AESTDTC, and...

  laura_archer

  JMP Knowledge Base |

  Jan 6, 2023 11:38 AM

  282 views | 0 replies