TM1 Forum

would you happen to have some guidance on how to structure that code to keep the Unassigned Clients element in the dimension.

Trevor, We did not specifuically write any code for this process.. I just used the tabs within the TI Process Creator. Below is the some code on the various tabs under Advanced that was auto generated. ProLog #****Begin: Generated Statements*** DIMENSIONDELETEALLELEMENTS('TestClient'); DIMENSIONSORT...

WE have a client dimension with 2 hierarchies. One hierarchy is called Total Clients and the level below that would be each of the parent codes for our client listing. Under each parent could be 1 or a handful of local client codes. Also under this Total Clients level, we would have an element calle...

our data load is an ODBC connection to our SQL database where we are pulling data from a view. We have a number of fields in the view, one which is Client so I would guess that the Clientfield from the view would be the one I would use.

that was the route I was going. just to clarify, what do you mean by ClientValueFromFile within the formula?

We are looking as part of our data load process to update a dimension which is being tracked as an attribute of another dimension. I will explain below we have a client dimension where we have an attribute of industry for which that client belongs too. we have an industry dimension which contains th...

Our business units generate a Trial Balance in their own GL Accounts. They are then presented with a Cognos Express Xcelerator Excel template with the Account dimensions listed (different then the local unit accounts) and they manually copy and paste from their local file into the template and then ...

Thank you Jim. The service account we are using did not have access to that table.

We have a current TI process which pulls data from a 1 table with no issues. We are trying to point that query to a new table with the same fields that hold historical data, but when i change the FROM clause of the query to be the new table name, i receive the error message below. "SQL Statemen...

Yes I am using an existing view as the Datasource so I can take whatever is currently in the view and re-map to the new accounts. Again I am brand new to TM1 so I apologize if my questions are so beginner level.

I did not set up the view so I do not know the reason for the calculated rules. Can I go back and change the data source view to skip the calculated values as this point?

I have confirmed that the cube I am trying to update does have a rule associated to it. What I am really trying to do is just update the account number to be something new but the values are not being updated but just moving to be associated to the new accounts we have. I will try to check the condi...

So I was able to run the process, but it produced the following error message in the log file. There are a number of these errors in the log file. Any insight as to what this message means and how to fix? "Actual","Mar-2014","Current Budget Rate","Consulting",...

made that change and was able to get the error message to disappear.

thanks for the information

Sorry tomok for not being more clearer and I don't mean to waste your time and I appreciate your guidance and responsiveness to this post. I will try to be more clearer. Purpose: To take the current GL accounts stored in the cube and map them to a new set of GL accounts we have created. Steps Take s...

I have already ran thru the attribute setup for our account dimension and associated the new account number we want to map to. I have then tried to update or create a process to utilize that attribute but this is where I am getting stuck. any guidance?

We are running Cognos TM1 version 10.1 and we would like to setup a mapping table so we could map the current listing of GL accounts currently in a cube to point to a new GL account structure we have. I am new to TM1 so I was looking for some guidance on how to best approach these along with some te...