Simple Transaction Log Analysis: A GSheet Application Using the TM1 Rest API

I've always been intrigued by the possibilities the TM1 Rest API offers. While I am fully aware that existing solutions already query the transaction log files, I felt a personal call to navigate this challenge independently, driven by curiosity and the desire to expand my own understanding. So, I embarked on a project to employ the TM1 Rest API's capabilities and construct my own GSheet application. My ambition was not just to recreate what has been done, but to explore how I might further learn and potentially make this task into something perhaps more approachable and user-friendly.

I attempted to make this application simple. Users are given the ability to select a specific cube, identify an individual user, specify a date range, and choose an element from each of the cube's dimensions. This multifaceted filter ensures detailed and precise retrieval of transaction logs, custom-tailored to the user's analysis.

Let's consider this scenario. Suppose we're interested in understanding what modifications Tom has made in the Expense Forecast cube for Department 532 since July 10th. Using the GSheet application, users simply select the following:

  1. Cube: Expense Forecast
  2. User: Tom
  3. Date Range: Starting July 10th, onwards
  4. Dimension Element: Department 532

No alt text provided for this image
Date fields are Date Picker controls



The application then retrieves and presents the corresponding data.

No alt text provided for this image
Data is purposely masked

Observe how the GSheet application dynamically incorporates filters, further enhancing its functionality and user experience.

No alt text provided for this image
GSheet filters are added for each completed query

When the user opts for a different cube, the application purges prior results and updates to reflect the dimensions of the newly selected cube. Take, for instance, the selection of the Asset Forecast cube. The application refreshes the Dimension dropdown lists using the TM1 Rest API.

No alt text provided for this image
DImensions are updated when a different cube is selected

The application offers a way for users to pull custom transaction logs. It's equipped with basic yet helpful features like dynamic filters and auto-refreshing dropdown lists, thanks to the TM1 Rest API. Thank you for reading!

Jim Naff Please post this into the IBM Planning Analytics Experts group here on Linkedin - https://www.dhirubhai.net/groups/2492125/ #tm1 #planninganalytics #ibmplanninganalytics

回复
Vitalij Rusakovskij ?? ??

TM1 Academy | Business Solutions based on IBM Planning Analytics | Support in TM1-Projects

1 年

interesting #useCase, thanks Jim Naff for sharing your #idea!

回复
Vlad Didenko

TeamOne Google Integration for IBM Planning Analytics | Succeedium Planning Analytics Cloud Extension (SPACE)

1 年

Well done Jim! BTW this functionality is available in #TeamOne #GoogleSheets add-on for #IBM #PlanningAnalytics, you can easily view, search and export #TM1 server #Message, #Transaction and #Audit logs: https://succeedium.com/teamone/doc/logs #TeamOne allows filtering records before fetching them from the server. You can filter by element patterns too, as in your example, you can filter transaction log records by asset accounts containing "A15" or even combine multiple patterns: "A15", "A50", etc. #TeamOne can connect to multiple #IBM #PA #Local or #Cloud instances. You can even login with your IBM id (SSO). No installation is required. Available in any Google Sheets document.

  • 该图片无替代文字
Christoph Hein

Managing Director at Intito | Expert in Finance & Sustainability Planning | TM1 Fanboy | Advocate for a Sustainable Future

1 年

Very interesting use case. Thanks for sharing Jim Naff. Do you want to share the technical details as well?

要查看或添加评论,请登录

Jim Naff的更多文章

社区洞察

其他会员也浏览了