I can confirm the transaction log query is still on the to-do list for Workspace modeling.
We should provide a single transaction log UX that is accessible from both the Workspace TM1 model tree, similar to Architect, and the cube viewer. For the cube viewer, we should support transaction log queries from leaf cells and tuples (row and column headers with leaf level members).
It is possible to query the TM1 Servers transaction log using the ODATA API with a tool such as Postman. Here is an example of an ODATA API call against the Planning Sample model:
/api/v1/TransactionLogEntries?$filter=TimeStamp%20gt%202021-08-12T04:00:00Z%20and%20TimeStamp%20lt%202021-08-13T12:51:51Z%20and%20Cube%20eq%20'plan_BudgetPlan'%20and%20Tuple/any(t:%20t%20eq%20'42201')%20and%20Tuple/any(t:%20t%20eq%20'FY%202004%20Budget')
------------------------------
Stuart King
IBM Planning Analytics Offering Manager
------------------------------
Original Message:
Sent: Thu August 12, 2021 10:53 AM
From: Brian Simpson
Subject: Transaction Log in Workspace
We've implemented a few solutions where we load the logs into a relational database for querying. In theory you could also load them into a PA cube (assuming the volume of records isn't too high).
As Declan pointed out, it's on the roadmap and I believe one of the last things that you can do in Architect that is yet to be implemented in PAW :)
------------------------------
Brian Simpson
Original Message:
Sent: Wed August 11, 2021 08:06 PM
From: Adam Havas
Subject: Transaction Log in Workspace
Is there a way in Workspace to explore the Transaction Log? I haven't been able to find a way, so I default to going into Architect.
------------------------------
Adam
------------------------------
#PlanningAnalyticswithWatson