TM1 Forum

Just closing the loop -

Thank you Steve for the above support. I was able to update my code and get the desired results to fire correctly.

Thank you again,
Michael

In this situation you would add an attribute to use for the mapping. sPeriodToWriteTo = Attrs ('PERIOD MAIN' , vPeriodInSource, 'Mapping Attribute to PERIOD MONTH MAIN'); CellPutN('CubeAInput' ,..... sPeriodToWriteTo.....); If it is just that your source has YTDs at leaf and your destination moveme...

Good Morning Everyone, I have a manual Excel process that retrieves data from Local Cubes, then combines that data with manually-input values and pushes the updated values back into the Local cubes. So, in an attempt to semi-automate the process via TI processes, I built two cubes (let's call them C...

Thank you all for the suggestions. I am just finishing up month-end, but will pivot to development efforts shortly.

I greatly appreciate it!

Michael

Good Morning/Afternoon All, I am in the process of creating a new cube, which will replace one that contains fewer dimensions, etc. Before I make the switch from CUBE123 to CUBE456 I want to ensure that all processes, TI processes, rules, security, etc., have been migrated to the new cube. Is there ...

If you are going to be renaming processes, you may want to consider naming your processes with } prefix to denote system objects. Normal users will not see them unless the explicitly show these and have applicable security. If you are using PAW, there is an option to create system objects now too. ...

Good Afternoon Vovanenok, Thank you for the quick response! It sounds like the path that I took, while painful, is the correct path. I'll run into additional headaches when renaming "Cube A" to "Cube A Historical" and "Cube B" to "Cube A". Though, I wonder if ...

Good Afternoon Everyone, I have an existing cube with a number of views, TI processes, etc., along with the rules file and security settings. I was tasked with adding a dimension to the cube, but in my research it pointed to using a "IBM TM1/CX Planner Applications" Performance Modeler sol...

Good Morning All, Sorry for the double-post. That is exactly what the query was looking for with respect to defining the "Current Year" member as a string value. Here is the final code for reference: {FILTER( {FILTER( { TM1SUBSETALL( [PERIOD MONTH MAIN] )}, [PERIOD MONTH MAIN].[FORECAST MO...

You could try something like this: {FILTER( {FILTER( { TM1SUBSETALL( [PERIOD MONTH MAIN] )}, [PERIOD MONTH MAIN].[FORECAST MONTH] = "FORECAST") }, RIGHT([PERIOD MONTH MAIN].[PERIOD MONTH MAIN].CURRENTMEMBER.NAME,2)=[GLOBAL VARIABLE].([GLOBAL VARIABLE].[Current Year]) )} )} No guarantees -...

Good Morning Everyone, I am in the process of writing an MDX expression that filters my PERIOD MONTH MAIN dimension based on two conditions. The first being where the attribute of FORECAST MONTH contains "FORECAST" and the second condition based on a wildcard search for "22" whic...

Good Morning Everyone, When I looked at the Import Options (see attached) I initially thought it referred to the data type itself as String versus the element when being added to the dimension as either N for leaf (numeric) or C for consolidation. I rolled back my changes to mirror PROD, then went b...

Hello gtonkin, Thank you for the quick response. I exported the entire dimension to CSV, then used Notepad++ to add the new periods/hierarchies. I'm not sure it mattered or not, but I positioned the new members at the top of the file. I used PAW to rebuild the entire dimension, but after re-building...

Hello Everyone, My normal approach for adding elements and attributes has been to edit the dimension and manually add them. This works for one-off, minor modifications; however, in lieu of a future-state MDM approach. I am looking to either use PAW or a TI script to add future years to multiple PERI...

Good Morning Paul, Yes, the intent of the rule is to prevent all users from being able to access salary-related information. However, if the business decides to change course and only allow a select number of users (I.e. HR and Finance) to be able to drill into those transaction-level details then y...

I am in the process of implementing drill through functionality; however, I want to prevent end-users from selecting any leaf level or consolidated level accounts under the "Total Compensation and Benefits" hierarchy and executing the drill through process. So, I set-up a Drill Through rul...

Hello Declanr, With your theory in mind, I reviewed the process again and it looks like I was indeed running the "Other" category twice. The initial run was as a subset that ran during the WHILE clause and the second run was during the " IF(category=OTHER) then 1 minus OTHERPCT "...

Struggling a little bit to follow exactly, but can you share a bit about where this code is in the TI process? One theory is that if your code is on the data tab and being triggered more than once AND if "Other" is a child of "Control Total" - then on its first run it could put ...

Actually, looking at the results closer, it appears to be putting in a -0 value under OTHER. I am looking at my syntax to see if I put too many parenthesis or if my logic is written incorrectly somewhere else.

Good Afternoon Everyone, I am in the process of writing one or (potentially) multiple TI processes to replace an Allocation Spreadsheet. The spreadsheet performs A divided by B calculations for specific channels and pushes the results into a separate cube. I am able to complete those calculations wi...