MariusWirtz
commented
7 years ago Hi,
What you are getting is the proper Memberuniquename. This is by design. Cell-data in the TM1 REST API is linked to Members, not Elements.
This is because data, that comes through the TM1 REST API, is arranged in cellsets. Cellsets conist of axes and cells. The axes consist of tuples of members.
I agree, it would be more convenient if the REST API gave us the element unique names instead of the member unique name. But there is yet no way to query values with their corresponding coordinates as Element unique names. Or at least I am not aware of any.
For now the only way to go is to convert member unique names to element names in python. It's pretty straightforward:
from TM1py.Services import TM1Service
with TM1Service(address='', port=12354, user='admin', password='apple', ssl=True) as tm1:
mdx = 'SELECT TM1SubsetToSet([plan_source],"budget")*TM1SubsetToSet([plan_exchange_rates],"local exchange rate")*TM1SubsetToSet([plan_version],"FY 2004 Budget")*{[plan_department].Members}*TM1SubsetToSet([plan_business_unit],"n level business unit")*TM1SubsetToSet([plan_chart_of_accounts],"n level accounts") on ROWS, TM1SubsetToSet([plan_time],"n level 2005 time") on COLUMNS FROM [Plan_BudgetPlan]'
cellset = tm1.data.execute_mdx(mdx)
new_cellset = {}
for members, cell in cellset.items():
elements = tuple([member.split('].[')[-1].split('^')[-1][0:-1] for member in members])
new_cellset[elements] = cell
print(new_cellset)
Hope it helps!
Cheers,
Marius
glenoconnor
vviau
Hi, Thanks for creating this package! We will be using it in several ways. We're new to Python - so this issue may not really be an issue:
When an element has more than one parent, the data.execute_mdx method pulls in unwanted hierarchy information. For example, we have an element '2017-01-15' with more than one parent. It comes through as: '2017-01^2017-01-15' In this case, '2017-01-15' directly rolls into: '2017-01', 'WE 2017-01-21' and 'All Days'
If '2017-01' rolls into more than one parent, you'll get another level of the hierarchy.
When an element has only one parent, it comes through as desired '2017-01-15' I can reproduce this issue in any dimension for any element - it just needs to roll into more than one parent. Is this a bug? or is there a way to not get the unwanted hierarchy info?
Here's my MDX statement... mdx = "SELECT {[Dailies Digital - Metrics].[Customer Traffic Volume], \ [Dailies Digital - Metrics].[Cart Starts Customer]} ON Columns, \ tm1filterbylevel(Descendants([Glance - Date].[2017]),0) ON Rows \ FROM [Dailies Digital] \ Where ([Dailies Digital - Version].[Actuals])"