TM1 Forum

Hi Pavo Thanks for confirming that your issue with locking in temporary subsets is only related to temporary subsets that are MDX based. We don't use of those. Typically our MDX subsets are for things like get all base elements or full hierarchy. These are created as permanent subsets as part of our...

Hi Pavo Interesting that you have still got locks when using temporary views and subsets. Surely creating a permanent subset is more likely to cause lock contention since that is a meta data event? If I understand you correctly, you are relying on the lock being relatively short by creating the subs...

Hi

Where possible use temporary subsets and views. This had a dramatic effect on our lock contention, not to mentioned clutter.

Hi Charlotte It really depends on your purposes but my gut feel is that you should avoid using a string measure. If you want one measure to roll up and the other not to roll up then you can do this Have one dimension with a consolidation A B C Have a measures dimension crossed with this with two mea...

Hi Maren If you are going to use RunProcess to set off 300 lots of Process A in parallel, then you aren't going to get that degree of parallel processing unless your box has 300 processors. Therefore I would not bother about the fact that an instance of Process A will not complete until Process B fi...

Hi Charlotte I am not sure what you are asking. If you want an element at the bottom of the hierarchy and you don't want values in this to sum up, then using a zero weight as Declan suggests is the way to go. However, if when you say the lowest level dimension, you actually mean the measures dimensi...

Vasek In your Data tab put a TextOutput( 'temp.txt', A_VNO_G_Rada ) ; Run the process and then look at the output in temp.txt and you will see what data it is getting Your screen shot only showed the source dimension in the title area. Is it possible that as Lotsaram says that you only have source d...

Hi Jim It doesn't sound like there is anything unusual in the model. The one thing you could try is perhaps temporarily knocking out the effect of any rules on the ElementAttributes and the Picklist cube by using an [] = STET. That would at least allow you to eliminate that as a possible cause. I gu...

Hi Jim Hope all is well with you. We are running PA 2.0.5 so even older and we have dimensions with 13000 elements and we are not getting a problem in TM1 Web. Is there anything special about this dimension? Some things that you might want to check : Does the dimension have chained consolidations su...

Hi

Either add a consolidation on top of your Cas dimension and implement my original suggestion
Or
Change your CellPutN to CellIncrementN, as you will be getting multiple rows from your data source and you need to add them all together in the target cube

Regards

Paul Simon

Hi There are a few things that could be improved. I note that the Source and Target cubes only have one dimension in common, as well as the Source having an extra dimension. You are reading from a cube that has one more dimension than the target but you are not specifying the source element in the A...

Hi In this case you don't use a Native View. You use an MDX query which is superficially like a SQL statement but not quite the same An example on the sdata sample database is SELECT {[actvsbud].[Actual],[actvsbud].[Budget]} on columns , NON EMPTY CROSSJOIN( { DRILLDOWNMEMBER( {TM1FILTERBYPATTERN( {...

Hi It might be possible to do this using the Rest API alone by somehow filtering the results returned by the Native View. However, it might take you a while some help from Hubert to do that one. Alternatives are a) Execute an MDX Query - more complex MDX queries can use sub queries a bit like in SQL...

Hi Micheline I am not sure if Scott has some back ground info on your model. However, if you do have just two different consolidations within a classic dimension then you are not going to be able to achieve what you want as the sort order you set with DimensionSortOrder is going to apply to all elem...

Hi We allow users to upload data via CSV. We use a small VB.Net programme to do this. They get to this via a hyperlink from TM1 Web using the EXCEL HyperLink function which passes in the name of the Cost Centre etc to be loaded. The VB.Net is quite dumb. All it does is upload the file and to rename ...

Hi tsw Presumably, you are aware that if the user accidentally deletes an element, that they lose the data from the cubes, not just the element? Even if the element is a consolidation, deleting it will take it out of subsets, that can then affect views and in turn processes. It can also invalidate r...

Hi We provide the ability for users to update dimensions, but not directly. In my view it is easy enough for an experienced developer to make a mistake using the Dimension Editor, let alone an end-user. In our situation we have many contributors with their own local chart of accounts. They need to b...

Hi Sorry I missed the SUBNM in the post. Can you confirm it is a name not an index? You would probably still need it to be an index for it to show the revised element selection. In the process that adds the element do you have a RefreshMDXHierarchy( vDim ) in the Epilog? Another possibility might be...

Hi You didn't show the SUBNM Does it by any chance identify the element in something in double quotes rather than an index number? If the value for the element is given in quotes, then it will always show that value whether it is in the subset or not. It you give an index it will show the element at...

Hi For a month level dimension I would definitely combine year and month into a single dimension. By using named hierarchies you can still get a Year and Month cross tab if appropriate, but with all in one dimension you can do calculations like a 12 month rolling average just by consolidation that y...