TM1 Forum

When we have a user to select paramaters that are used in a TI to generate a Temporal Dinamic View of a cube, and we run a process using this dinamic view, and the process executes a Cellget - CellPut… if we do not go to the cell and write down at list one a number or something, the process does no...

I changed the picklist to static::A:B:C to show the empty value as well. The empty value shows up in Perspectives but when I select it, the blank value is written to the excel cell and overwrites the formula instead of writing the value back to the cube. If you will create the Static Picklist like ...

Strange, have you been using the same computer for Account 1, 2 and 3?

Also check if these accounts have the same Security setup within TM1

Please clarify your question. Are you asking about the BatchUpdateStart/BatchUpdateFinish or are you inquiring about using TM1 in Bulk Load Mode?

There is a PMR related to this issue.

http://www-304.ibm.com/support/docview. ... wg1PM24820

Only users with Administrative privileges have access to the Admin console.

Make sure you are logging in as the ADMIN.

Nick_Blommaerts wrote:Problem is that if you create a dynamic subset in a TI and assign it to a view, it will cause the TI to throw an error (which surprise surprise, you cannot handle in TM1

You can create the dynamic subset in a separate TI and then use that subset to build a View in another TI.

This error looks familiar but I got it a while ago (version 9.5 or prior) and what I recall I had to rebuilt the dimension. Did you check the }elementsAttributexxxx cube? I am assuming it would be showing you the same info as the screenshot.

The MDX statement which you have written does not seem to be right. Suppose if you want to filter on Dim3 then you will have to put Dim3 within TM1SubSetAll(). This will tell the MDX on which dimension you are working on. Later you apply Filter() in the MDX - when you apply the filter you skip Dim3 ...

In the TM1RPTROW function you can pass a MDX query which can apply filters on the query and your results will be displayed in the Active Form

The suggestions above will be useful.

On the other hand if you implement the Integrated Security then in that case you will not have worry about managing user passwords within TM1 as they will be authenticated externally (LDAP, Cognos, Active Directory etc.)

You will have to write a MDX statement specific to you requirement. Example is: Filter( TM1FilterByLevel(TM1SubSetAll([YourDim]) , 0) , [CubeName].( [Dim1].[Element] , [Dim2].[Element] , [Dim3].[", $B$4 , "] , [Dim4].[Element] ) <> 0 )

One thing in your screen shot which I have noticed that your element name is 1. (with the dot)

In your case the best practice is to create the element names without the dot so that your element is 1 not 1.

By looking at the sample error and screen shot you have posted it looks like the element in the dimension and the data in the CSV file are not matching with each other. You have Sep-06 in the CSV file while in the dimension you have Sep 2006 . Because these two are different that is why you are gett...

You need to create a cube which has Period dimensions (containing the Years and Months) and Day dimension.

See the sample screen shots for Period and Day dimensions.

This should give you a starting point....

mincharug.shulft,

Have you checked the tm1server.log file? What does it say?

I havent tested it in 10.1 but there is a setting in the web.config file which allows you to set the column width Look for the following in the web.config file: <add key="CubeviewerStringWrap" value="Enabled=true;MinCharactersToWrap=20;MaxDisplayCharacters=200;WidthOfWrapCell=50"...

This might be because of the Excel cell Dependencies - when a cell in the spreadsheet refers to another cell in the spreadsheet. In such cases the dependent cell must be calculated after the source cell to which the depend.

Make sure the credentials for the Widows Service account are correct. or else you can choose the option of "This Account" in the Service properties.

Your assumption is right Excel and TM1Web give different results. This is because TM1Web has to render the Excel spreadsheet into XML. After this rendering you will see some differences in the web browser. If you see #### for the large numbers in that case you can leave some extra width in Excel or ...