TM1 Forum

Wim Gielis wrote: ↑

Wed Jan 06, 2021 8:02 pm

We both think Steve’s reply is already what the OP needs

Yes, absolutely. Would not have even responded if I'd read it more closely. It suits me to just delete the extraneous posts.

We have seen performance of MDX views vs. standard/classic views to be poor. Looking at your MDX code, it does not appear you are using alternate hierarchies, so building a classic view should not be a problem. I would suggest trying that. I believe the performance problem is directly related to wh...

We have seen performance of MDX views vs. standard/classic views to be poor. Looking at your MDX code, it does not appear you are using alternate hierarchies, so building a classic view should not be a problem. I would suggest trying that. I believe the performance problem is directly related to wha...

To list the elements of an element something like the following is a simple approach in a TI: dimApprovalHier = 'dimName'; sComponentElementName = 'MyChildElement'; sOutputFile = 'ListOfParents.txt'; nParents = ELPARN(dimApprovalHier, i = 1; While (i <= nParents); sParent = ELPAR(dimApprovalHier, sC...

Merry Christmas to All!

And my most fervent wishes for a very Happy New Year!!!

And very heartfelt adieu to 2020. May we never see the likes of you again.

Alan Kirk wrote: ↑

Wed Dec 09, 2020 10:34 pm

That's like saying "The charge of the Light Brigade may not in fact have been a tactically prudent exercise".

I literally laughed out loud at this. And, in a coincidence, watched the movie with Trevor Howard and Sir John Geilgud this past weekend. Howard was over the top.

Do you have a direct line to Stuart King on this issue? I do not have a direct line to Stuart King. As a contractor, I have to pass my findings/issues through regular staff, but they are knowledgeable and the firm has a substantial relationship with IBM. I can't fathom why IBM seems to insist that ...

FWIW, and I have not had time to test, we think it may be centered around the measure dimension elements being cleared cannot be in an alternate hierarchy.

Or don't use parameters at all and read the values directly from the control cubes in the TI concerned....This problem would then disappear. IMO if you have the parameter for a TI in a control cube then parameterising the TI is redundant and adds complexity. Alternatively treat all parameters as st...

Update. We have noticed a possible pattern with regards to output order not matching dimension order when reading an MDX cube view: We are observing the output order is by: 1) dimensions that are based on the default hierarchy (dimname:dimname) then regular dimension order. 2) dimensions where the M...

Tom, Agreed. Here is what I was really trying to do: IF (nNumberOfParams = 1); ExecuteProcess(sProcess, CellGetS(cubProcessControl, sProcess, '0', 'ParamName'), IF(SUBST(CellGetS(cubProcessControl, sProcess, '0', 'ParamName'), 2, 1) @= 'S', CellGetS(cubProcessControl, sProcess, '0', 'ParamSValue'), ...

TM1TupleSize maybe? This code will return the unique leaf elements of the subset: TM1FilterByLevel(FILTER( [pProduct].[pProductSubset], TM1TupleSize(INTERSECT([pProduct].[pProductSubset], {[pProduct].currentmember}, ALL).item(1)) = 0), 0) To find those that exist at least twice: TM1FilterByLevel(FIL...

stiill the same error : vDimension='Invoiced Partners'; vSourceSubset=vDimension| ' All N'; vMdx= '{TM1FILTERBYLEVEL( {TM1SUBSETALL( [Invoiced Partners] )}, 0)}'; if(SubsetExists(vDimension,vSourceSubset)=0); SubsetCreate(vDimension,vSourceSubset); Else; SubsetDeleteAllElements(vdimension,vSourceSu...

I want to assign either a string or numeric value to a variable depending on a conditional test. I am somewhat surprised TM1 complains about this code reporting that vS: invalid numeric expression when trying to save the TI. vParam = 'pnDebug'; vtest = IF(SUBST(vParam, 2, 1) @= 'S', 1, 0); vN = Cell...

Steve Rowe wrote: ↑

Thu Nov 12, 2020 5:13 pm

Thanks Ty, great work on narrowing this down and reporting back. Pretty challenging space to work in...

I'm assuming it is the last dimension in the built order rather than a re-ordered to last dimension?

Thanks, Steve. Yes, it appears to be that dimension only.

Have not tested, but suspect this may be related to the feeder problem related to alternate hierarchies on the last dimension in a cube.

viewtopic.php?f=3&t=15576

Once last comment. It appears that alternate hierarchies on dimensions other than the measure (or last) dimension in the cube do not break shorthand multiple target feeders.

Add an alternate hierarchy to the measure dimension, however, and feeders will have to be examined. We have submitted to IBM.

Additional information with more testing to come: In the initial testing, the dimensions involved had alternate hierarchies. In the second round of testing with the feeders working as expected, the dimensions did not. Added an alternate hierarchy to the measure dimension with a single leaf element. ...

Well. Today, everything I described above as failing is now feeding correctly. One of the other team members was investigating this further and reported the problems were no longer appearing. Multiple targets, shorthand notation, chain feeder (A => B => C) and (A => B => C, D): all working. MTFeeder...

I haven't tested this, nor do I say it's intuitive and needed and easy, but if we do a DimensionDeleteAllElements and insert them back in the correct sequence - I *think* this could work. I believe you are correct in your thinking. As long as all the dimension changes occur in the prolog and METADA...