Tiny Tricks with Data Connectors

[#1]

The new Data connector Concept in JMP is very helpful:

- within a few minutes (and a willing AI) a user can create any data connector they want. Here is a wonderful introduction by Brian Corcoran: Build a Python-based JMP Data Connector in Minutes (2026-EU-30MP-2638) 

- The data is piped through Query Builder. Together with the data, the user gets a working UPDATE functionalitiy.

- ...

here are some tricks:

[#2]

Trigger the Python Package installation again after a first installation:
e.g.:

• You installed the Addin in JMP v19 , but the Connector doesn't work in JMP v25?
• you installed an update of the AddIn but the Python Package is still the old one 

-> delete the file 'INSTALLED_TO' or "xyz_installed.txt" from the AddIn Directory.

[#3]

You added a new field via the python package, but after installing the new version of the AddIn the new field is not visible in the GUI of the Data Connector.
-> close JMP and try again.

[#4]

Unfortunately, there is a one drawback with Data Connectors: Subfolders!
How to access the right file?

First-level subfolders can be interpreted as schemas, but deeper levels are not accessible.

The current workaround: 
save a dummy data connector once.
Don't use Connect to use the Data Connector, instead click on Edit, enter the current folder manually, then click Connect.
(don't save with the new settings)
-> Connection will be opened for the specific folder

This approach feel complicated - compared to a standard Windows/Mac file dialogue to select an arbitrary file/folder 
 [Discovery Summit Europe  2026]: there are plans to work on this issue

[#5]

It is true that we only support 1 level of drill down (Schema/Table) now with the dialogs and design.  We are considering how to fit in multi-level while still maintaining familiarity for those traditional DB users who already have what they need.  Thank you for the feedback.

Brian