TM1 Forum

ViewRowSuppressZeroesSet is meaningless in a TI because there is no concept of rows OR columns in a TI process that is sourced from a cube view. It is only valid in a cube view while in the user interface (Perspectives, Architect, TM1Web). A TI view is always treated as a flat source, meaning you g...

Apologies.. the feeders are there which i did not put in the example above...The values are correct and not indicated as 'unfed' etc... Are you using persistent feeders? If so, shut down, delete the .feeder files, and restart. Also, make sure that if you're using conditional feeders that MaximumCub...

I agree with tomok, this is a feeder problem. Also, please read the Request for Assistance Guidelines , particularly #5. Abstracted questions are difficult to answer (but in this case the root cause is obvious). I know you think you're making it "simpler" but you're not-- you're obfuscatin...

With a few exceptions, I've found everyone at support to be competent and pleasant, but the result has been far from meeting my expectations. This screenshot should illustrate why. I guess at least they have recent "modified" dates, right? Right? Granted, the first one I graded Sev4, but t...

Looks like temporary objects don't work with a dynamic datasource (building the view in the prolog and using DatasourceNameForServer / DatasourceNameForClient / DataSourceType='View' / DatasourceCubeview. Bummer, that's a huge percentage of my use case. Now I have to decide if it's worth refactoring...

[quote="hiraniha"I have always steered clear of persistent feeders, for reasons that I'm sure many would have counter arguments for, so won't even mention them. :D[/quote] In my experience, PersistentFeeders has been very stable. I did have one issue related to a rule/feeder change that di...

I tried the lookup as suggested, it didn't make any noticeable difference to the start-up times. Yes, in retrospect that would only affect rule calculation, not feeder/startup time. I have revert to an unconventional solution. I have used a single measure called Day_Flag, which is fed if any calcul...

Two suggestions: 1) Do all your versions need to be dynamic? A quick way to eliminate a lot of feeders (and calculated cells) would be to freeze of data that's not subject to change. Not sure if you're doing this via your feeder-- it's hard to tell since you're not explicitly identifying dimensions ...

At the risk of liveblogging my efforts, here's another update. I refactored the old processes into five new processes grouped into three sets. The first process creates the new element and the subset for the source element. The next one walks through the cubes-- when it finds a cube with a version d...

I'd have three, the first preparation job is the one that is most likely to trigger a lock, but if it is not chained to the export job then the lock will be very short. The export and import jobs need to do as little as possible, almost just an asciioutput and cellputn. gl! not a Friday afternoon j...

What happens when you execute your process in Bulk Load Mode ? Does that make a difference regarding performance ? Every time I've tried this it hasn't gone well, and today was no exception. Added EnableBulkLoadMode as first line in Prolog and server made to it the end (based on export files) befor...

I'm running into some locking issues on TM1 x64 10.2.2.3. I have a process that makes a copy of a version (i.e. a snapshot). Algorithm is: Via parameter, set source version which is used to create a subset in version dim. Target version element is automatically created, name based on current datetim...

I ran into an issue last week where I was feeding a consolidation and a newly added base element wasn't being fed, even across restarts. I was able to resolve it by stopping the server, deleting the .feeder files, and restarting.

Matt

Nothing jumps out at me. Is this a copy/paste or a retype?

Please a) stop opening new threads for the same problem and b) read the request for assistance guidelines.

Sorry I was not clear enough. I'm trying to convert an existing rule into an in-cube calculation, the new feature of Perf Modeler. In this editor the syntax is like : [dimName]:[elName] and I can't find a way to tell something like : [ [dimName1]:[elName], [dimName2]:[elName] ] Syntax is ['dimName'...

Also, your two threads on the same topic have now been merged together. Please do not open multiple threads on the same topic.

when we went with "Update Dimension - Yes ", processes were taking tooo much time and one or the other process getting stuck.. My guess is your datasource is very slow. When you have code on the metadata and data tabs TM1 pulls the full dataset from the source system twice, once for each ...

Cube "DM" has the following dimensions : !Customer, !Month, !Year, !Plant, !Product aggregate, !Version, !DM ['All Currencies','Dummy_plant','Volume'] => DB('DM',!Version,!Customer,!Month,!Year,!Plant,!Product aggregate,'Sales'); Assuming you listed the dimensions in your cube in their co...

I really, really hate these hypothetical code examples. How can anyone help you without the real stuff? Please post the complete dimensionality for all three cubes and the actual rule statements, including feeders. Agreed. It's not uncommon for someone to have the concepts right and when cobbling t...