GetSessionID Turbo Integrator function

With TM1 Database 12, the introduction of the "ExecuteHttpRequest" has opened the door for many new and exciting possibilities within TM1. One of the possibilities is the ability for a Turbo Integrator process to make an HTTP Request against it's own TM1 Database. Currently to do this a significant amount of authorization handshake requests, connection conditions for different deployments, and the need for those connection authorization details to be stored in a place where a TI could retrieve it, the ease with which this can be done is severly limited. Not only that, but the HTTP Request that comes from the Turbo Integrator process would create a new session, when it already has a session.

And so, adding a "GetSessionID()" or "SessionID()" function, similar to "TM1User()", would allow a Turbo Integrator process to easily Authorize and maintain it's session context when executing HTTP Requests to it's own instance. Another support function to this end would be "GetConnectionURL()", but that is less necessary.

The benefits and value this has would be tremendous. There are a significant number of features in TM1 that the Rest API has, that Turbo Integrator does not. This is partly why external tools like TM1py are so useful/valuable. To list a few:

• ExecuteMDXExpression against the database instead of against a dimension, like what "SubsetMDXSet" requires.

• Access to Cellsets and Cells!!

  • Reference/retrieve data by Cell Ordinal instead of Elements.

  • Convert MDX Views to Native Views

  • Get Cell Count of Views

  • Interact with Cell Format Values and Formatted Values

  • More Data Spreading Operations

• Query/Check feeders of a Cube/Cell

• Chore Manipulation

• Server Configuration interaction

• Git interaction

• Database wide thread management

• Execute unbound TIs

• And many more!

All of those features are at the abstract level, to give a more practical list:

• Prevent a TI from calling too many subthreads, which can lock users from being allocated threads

• Copy data between cubes by ordinality instead of elements, eliminating the need for complex mappings

• Increase efficiency of TIs by converting MDX views to Native Views

• Statistical Analysis of Sparsity/Data through cellcount

• Feeder Analysis

• Create and modify Chores

• Automate Git exports for version control

Enabling all of these features and capabilities can be done with one simple step: implementing the 'GetSessionID' function.

Thank you,

Ben Dunleavy