TM1 Forum

Feeders are independent of the value (or non-value) stored in the cell. Regardless of whether the cell is blank or zero, if it is fed, TM1 has to deal with the overhead slowing performance of the consolidations. This is why feeder design is so important. There is nothing inherently wrong with storin...

Unless I misread your question, the result you got is the one expected. If you have a look at the documentation for CreateHierarchyByAttribute , you'll see it's very limited in what it can do. It can create a 3-level hierarchy, with level 0 being your leaf elements, level 1 being the value of the a...

Well, here is an update on this. As stated, there was a set of elements that were being ignored by the CreateHierarchyByAttribute function in a TI and through PAW, which I understand uses this function through the API. So, as it turned out we do have a single dimension for which we use this function...

macsir wrote: ↑Wed May 19, 2021 8:41 pm Just curious, what PAW and PAL version do you use?

PA: 2.0.9.1
PAW: 2.0.53

Having a problem with this function, as well as the manual method of creating an alternate hierarchy on an attribute through PAW. My time dimension has consolidations by year (2018, 2019, ..., 2023) with child periods of 201801...201812, 201901...201912, etc. Added an attribute called MonthName and ...

Your profile says you are on version 9.5? Is that true?

Have you looked at the TI CubeDataReservation functions? These will apply security to any slice of a cube and can be managed with TIs. I've tested them to see how they work, but have not actually used them in practice, so not familiar with their pros and cons. They did not seem overly difficult use.

I think that advice is a little out of date and has been debunked via analysis now available with }StatsByRule. An attribute lookup is not faster than a string rule or numeric to string conversion. However, in terms of readibility and maintainability it woudl still normally be the recommended appro...

"Nothing from nothing leaves nothing"

-Billy Preston

Who knew Billy was a TM1 expert back in 1974.

DB(), as in your example, is faster than ATTRS as well in every test I have ever performed.

Not that I am aware of but I will double check. Did you raise a defect? Or just turn Persistent Feeders off? Steve, sorry, I went back and reviewed my notes. I conflated an issue we had a couple of weeks ago which was a perfectly normal and expected feeder behavior vs. the problem with feeding to a...

Steve, I ran into the same problem about two weeks ago. We use persistent feeders as well. Observed and did the same things you did in resolving.

Question on your case: are any of the rules referencing alternate hierarchies?

Elessar wrote: ↑Thu Apr 22, 2021 1:22 pm Hi,

You can use "load on Demand" parameter for this. Check it on every cube, and monitor the memory usage in }StatsByCube. The cubes which are not loaded - were not used.

Very cool idea.

There is an outlier on this that can significantly impact performance writing to a cube as well and that is dimension order, although with what appears to be three dimensions in the cube, this may be an unlikely culprit. The first thing that needs to be corrected is the subset needs to be static as ...

BTW, I don't like the idea of having prod and non-prod services sharing the same name. YMMV. My mileage varies greatly indeed. If I'm having users testing reports in a dev environment (especially complex reports which draw from multiple servers), websheets on TM1 web etc, etc, I want them using EXA...

I know you said the feeder is straightforward, but just to confirm, it does not have one of the elements using an attribute call to address a target cell does it? Second, if you process feeders on the input cube, nothing changes? A friend of mine had a problem with this yesterday with the difference...

Who can explain the below result ? The text file is the one generated by the TI process. 05.png Have not used the multi-language functionality (Southern English, aka: The Way God Himself Talks, is avoided in my naming conventions to avoid things like whirly-gig processes, hog waller cubes, shotgun ...

Extending on what Wim has pointed out, simplifying output (and assuming no numeric data that requires formatting: DatasourceASCIIQuoteCharacter=''; vTab=Char(9); vDoubleQuote=Char(39); asciioutput ( 'c:\file.txt' , EXPAND(%field1%%vTab%%field2%"%vDoubleQuote%s%vTab%%field3%' )); Or even: Dataso...

Ha! Another way to use that little-used TM1 MDX function, TM1TupleSize . So the scenario is this: a lookup cube that stores certain data and allows adjustments to data along dimension lines. For a simple example, imagine an Employee Information cube that has Employee , Job Title , Time and measure d...

We have pretty much the same issue and while you could do it the way you talking with unique consolidation elements, we do an extended variation of alternate hierarchies as mentioned by Declan. In our case, the business plans/forecasts at a higher level than individual accounts and cost centers and ...