Open .jmpquery Files Containing Snowflake Connectors and Choose to Use an Active Snowflake Connections in JMP Application

[MikeStevenson]

What inspired this wish list request? 

When a user opens a .jmpquery file, and it contains an unspecified Connection to an ODBC DSN, a Data connector Login dialog opens, and one option is to "Change Data Source..." If the user chooses this, they are brought to the ODBC data source panel, and If the user has already opened one or more ODBC DSNs, then they can choose to try to run this file and its queries with the already opened DSN.

If, however, there is a .jmpquery file and it contains a Connection to Snowflake REST API (or another OAuth based connection), as of JMP version 19.1 it always prompts for a new OAuth login. This means that someone who has logged in to a connection, may have to repeat this login for every file they would like to open and run against their active Snowflake connection.

What is the improvement you would like to see? 

I would like to be able to:

1. Open a new Snowflake REST API connection through the File > Connect to... > Data Connectors > New Connection... workflow.
2. Open a .jsl or .jmpquery Script from the File > Open or JMP Home menu that has a connection specified of type New Data Connector of Base type com.jmp.snowflake_rest
   
3. In addition to (or instead of) being prompted to login to the data connector, be able to "Change Data Source..." and be given the option to attempt with any currently open com.jmp.snowflake_rest type connections since the last start of the JMP Application.
   Reasonable timeouts may be necessary.

Why is this idea important? 

This feature would allow us to run important repeatable queries without having to login with each new file. This would save a lot of time.