TM1 Forum

Hello all

I run the TI to transfer the data from replicated cube to target cube. Now the data source view has different element name than in target. E.G.: ACCOUNT1 IS THERE INSTEAD OF ACC1 SO I APPLIED ALIAS IN THE TARGET CUBE TEST ACCOUNT DIMENSION SO DATA MUST BE UPLOADED ON THE BASIS OF ALIAS.

I have attach the TI process for you consideration. Let me know on what should i need to focus? Could you please let me know - when we do synchronize the data from mirror cube than what would be impact on main cube in different server(does the user experience would be affected)?

I take it the view created in the first process is teh source of the second? Are you executing these as part of a chore?

jim wood wrote:I take it the view created in the first process is teh source of the second? Are you executing these as part of a chore?

I did not set up a chore yet. I just write a process and test it but couldn't get desired result (eventhough process run successfully). Could you give one more thought on data tab in My TI?

Thanks

Dharav

Pretty much the first step in bug checking any issues like this is placing asciioutputs in your process to see exactly what records are getting processed; place on outside and inside IF statements and While loops and then try and look for anything where records you'd expect to see aren't there.

1. I would check if the Source View has any values since you have suppressed zeros.

2. Not too sure why your assigning subsets to 1i_Accounts cube, if no view has been created for this cube.

3. Also don't use Aliases to map the data, I would recommend using attributes instead.

Also, it is good to utilize the ASCII output function to debug your process and mentioned above.

Hello All

Thank You so much for your inputs. I found the problem and it resolved now.

declanr wrote:Pretty much the first step in bug checking any issues like this is placing asciioutputs in your process to see exactly what records are getting processed; place on outside and inside IF statements and While loops and then try and look for anything where records you'd expect to see aren't there.

Declanr, thanks for suggesting debugging approach through ASCII Output. I figure out that the data was there in sourceview but it couldn't come in to data file as the data was for consolidation element and one element which was based on rules. When i entered the statement under assigning subset to sourceview :ViewExtractSkipCalcsSet (Cube, ViewName, Flag) with 0 flag value, the data was there after process run successfully. I figure out this because of Ascii Output functionality you have suggested as above.