IBM Data and AI Ideas Portal for Customers
This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Specific links you will want to bookmark for future use
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
IBM Employees should enter Ideas at https://ideas.ibm.com
Yes I agree 100%
If you are considering using a paid solution, take a look at SPACE - Succeedium Planning Analytics Cloud Extension. It brings Python and TM1py to PAW: https://succeedium.com/space/
I second the call that this should just be "we need python integration in PAoC"
The use case seldom thought about by IBM is the need for PA to integrate into external SaaS data sources that do not have a direct ODBC connection. They are only accessible via API (or costly 3rd party connectors). Python is the natural fit to handle the authentication and data retrieval from those systems for presentation to the PAoC server.
Python environment can also be implemented as a kubernetes container / separate cloud offering providing a direct secure connection to and from the Data server. This will make it easily portable to the new generation of the TM1 server.
Here are some additional ideas to consider for this feature:
Turbo Integrator could introduce a kind of
ExecutePythonfunction, that takes a path to a py script and arguments.When a Python/TM1py script is kicked off, usually one of the first things that the script does is to authenticate with TM1. This usually takes a couple of seconds. If TI could provide a
"TM1 Session ID"orCAM Passportor some token that TM1py could use immediately to skip authentication, it would greatly improve the utility of this integration.2 seconds for authentication is not a lot, but for a user that clicks a button in PAW or TM1Web (perhaps multiple times) it can make a big difference.
Having Python and TM1py on the same box is not just useful so that `ExecuteCommand` can be used to call it, but it can also help with performance.
In a scenario where Python is used for a predictive forecast or a complex cost allocation large quantities of data are often moved between TM1 and Python. In that case it is beneficial if both applications are on the same box.
I would second the integration of Jupyter Notebooks and add too that integration should work across PAW, PAfE, PASS and TI in the TM1 Engine.
Not sure that the implementation need be different on PAoC, CP4D, local etc. Ideally integration should be the same to deploy throughout.
I think this RFE should be refined to simply read, "we need python integration in PAoC" and not specify that python must be installed on same server as PA. Personally, I envision some sort of solution like Jupyter Notebooks in Cognos Analytics.
One major requirement that this RFE implies but doesn't explicitly state is that we must have the ability to call python scripts from an action button (PAW or PAX) and be able to call execution of a python script from a TI process. This will allow us to call python scripts from enduser action as well as schedule as part of a chore. Currently both of these are easily done on-prem by simply having python installed on the same server as PA. The same can be accomplished in cloud by packing the python script in an exe and placing on the data folder to be called via ExecuteCommand, but recent comments in an AMA suggest that could be blocked and likely isn't an option in V12. Another option is to host the script on another cloud service such as AWS Lambda that you can then call via rest from TI (powershell in V11 and new TI function in V12). These are suboptimal workarounds in my opinion.